-
Notifications
You must be signed in to change notification settings - Fork 192
Determine lightweight SDK API calls #885
Comments
Hello, I did some research on this subject. Based on what we have in neon-wallet, neon-js and neo-modules, we need to implement these features if we want a complete light-weight SDK: Transaction support:
Transaction building:
API integration:
Wallet features:
Other:
|
Nicely done @lock9! Can you elaborate a bit more on:
|
Hello
https://scan.nel.group/
http://monitor.cityofzion.io/assets/testnet.json
Yes. Here is an example from neon-wallet: https://github.com/CityOfZion/neon-wallet/blob/dev/app/actions/nodeStorageActions.js
Exactly. After we send the transaction using
I think this is required if you are hosting a private RPC server and you want to allow only certain users to interact with it |
Going further: Transaction building:
Send native asset
SendMany
Split
Call contract with attachments
New - Test invoke.
Deploy smart contract
NEP-5
SendMany
Custom ('raw transaction') API integration: Neo RPC (2.9.0+)
NeoScan
NEL
Notification Server
CoZ Monitor
Wallet features:
NEP 6 - Account
NEP 6 - Wallet
Signing
Multisigning
Other: |
This is a TODO for a project (see side bar)
Create an inventory of useful/required API’s to interact with the blockchain without having to run a full node and propose a structure. The NeoModules structure/module separation has been indicated to be very useful by other users. Try to use that as a reference. For more ideas look at neon-js
The bare minimum functionality to support:
For RPC functionality keep #884 in mind
The text was updated successfully, but these errors were encountered: