neo-one
neo-one copied to clipboard
neo-one-suite
The One for easy, fast, & fun NEO app development.
The available RPC server methods needs to be thoroughly tested. Probably tested by running Client API tests or by creating RPC server tests. See `createHandler.ts`
- Need to make sure we’re calling contracts correctly in our client ScriptBuilder - If sticking with current hack-y version: - All method offsets are set to zero (improper) -...
after #2096 we should look into adding an integration test for neo-one which tests a contract on the testnet. This wouldn't be run in CI, it would be specifically for...
Check that the `trusts` array/wildcard container being created by the compiler and parsed/used by the client is all correct.
Need to find everywhere that we currently/previously computed a contract's address, like: - `compileContract.ts` (incorrect? see comments in code) - `LocalUserAccountProvider.ts` (correct?) - `startNode.ts` (incorrect?) Then use the information gathered...
The receive decorator did a lot of work behind the scenes with native assets, especially with allowing a way for callers of the contract method to get their assets back...
We should probably add a way to get arbitrary notifications from any contract with something like `Notifications.from(Address.from())` which will return an array of builtin `Notification`s for the smart contract to...
### Description of the Change - Work-In-Progress: adding a popup to the legacy website that notifies the user that neo-one.io is for Neo Legacy and that N3 docs can be...
In RC4 NF found and fixed a bug in `Crypto.VerifySignature()` having to do with EC curve differences on macOS vs Linux/Windows. But it appeared to me that there was no...
Metadata
Owner
Metadata
The One for easy, fast, & fun NEO app development.