-
Notifications
You must be signed in to change notification settings - Fork 165
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[NEO 3.0] neon-js should support the coming NEO 3.0 #441
Comments
UPDATED ON 26/07/19 NEO3 Proposal for NEON-JSCurrent Structure of neon-jsTargets:To support NEO3 in neon-js. NEO3 featuresDocuments: https://github.com/Tommo-L/NEO3-Development-Guide
Timeline
Plan
Structure of neon-js for NEO3Any suggestions and comments would be appreciated. |
I think depending on how the native assets are reimplemented, we might consider merging nep5 into the core set of modules. Also, with regards to publishing, we can either use a new namespace (cityofzion/neon3-js?) or just do a breaking change with v5 being the the compatible version with neo 3.x. I doubt smartContract will end up under
|
@snowypowers Thanks for your reply.
I suggest the latter. Here's my plan:
I plan to integrate So |
|
|
neon-js/packages/neon-api/src/funcs/main.ts Lines 42 to 50 in 8972f6f
@snowypowers How about employing generator to replace this promise style in NEO3 high level API? So that user can have more control over the flow(like using different param according to certain middle state), and he can add parameters gradually instead of passing params all at once.
|
Now that low level APIs are merged into
Any suggestions would be welcomed. |
For fees, since its going to be inaccurate to calculate the fees, I rather not do anything offline. We can add another step after constructing the transaction to add the fees. With regards to 469, its too many features. Lets start with the TransactionBuilder which is pretty essential and build up the workflow first. Not clear on the structure of NetProvider, it looks a little weird that you have Entity Provider inherit off it. Having a facade is a good use case though. |
@snowypowers A NetProvider instance is a net-specific(mainnet, testnet, privatenet) provider that can deal with some read request(e.g. balance, height) with neo, in which case an account(private key) is not needed. Considering most cases where user use sdk with specific net and specific accounts, it is not necessary to isolate all the requests, the network info and account info are usually fixed. That's the point for this design. |
It's recommend to set the contact information about the contract in manifest file, as neo3 have moved those properties, replaced by |
NEO 3.0 road map is released. And hopefully NEO 3.0 testNet will come out in this July.
NEO plans to draw lots of communities and developers to develop tools and dApps on 3.0 testNet, in which SDK will act an important role.
Now NGD members are developing 3.0 C# SDK in project neo: neo-project/neo#850. I think neon-js should be upgraded for 3.0 at the same time, because neon-js developers could request support from developers of C# SDK, as they could modify core codes properly to support SDK if necessary.
The text was updated successfully, but these errors were encountered: