Jimmy
Jimmy
The behavior of the docker test appears to be unpredictable, as it has shown inconsistent results after being run on the same code multiple times - sometimes passing and sometimes...
this is from @lock9, i think he presents the guideline better than me. **Development Process Guidelines** 1. **Voluntary Issue Assignment**: - Core developers may voluntarily take on new issues. -...
## Core Development (coredev): 1. Set up a blockchain technical committee - The technical committee responsible for the technical direction of the NEO blockchain. 2. NEO Specification (Yellow Paper) -...
**Summary or problem description** It has being painful to maintain multiple projects while every single one of them has some sort of relyance on others. It is hard for new...
**Summary or problem description** As is known to the community, it takes a few days to re-sync the neo ledger, it is not only painful, but also dangerous for nodes...
This amazing idea is from 17v. By enabling developers to write and run script in the neo-cli, they are empowerd to directly interact with the leder and smart contract directly...
## Problem Statement Currently, the NEO ecosystem lacks a standardized callback mechanism for smart contracts to handle incoming NEP-17 token transfers. This leads to fragmented and less secure implementations across...
Based on EIP-712, propose neo's standard meta transaction format. Major difference: chainId = > networkId, data = > script. '''Data Structures''': * '''Domain''': ** `networkId`: Integer representing the NEO network...
This pr focus on implement NEP11 and NEP17 callback standards. Wait for https://github.com/neo-project/proposals/pull/169
The devpack has been facing numerous significant issues. These include incomplete compiler syntax support, vague interface definitions, lack of comments, cumbersome code structure, absence of tests, insufficient documentation, lack of...