[Feb. 05] Core Dev Regular Meeting Discussion

[shargon]

@neo-project/developers

Meeting held in google meets.
Same time as always. 05.02.2026 9:00 AM EST

Meeting Agenda:

• [N4] Adapt neo-node to Neo 4.0.0 neo-node#989
• Proposal: Remove Voting Rewards and Introduce Native Staking Rewards #4467
• [N3] Port 4318 fixes VerifySignature, VerifyWithEd255519 and VerifyWithECDsa #4449
• dNeo (Decimal Neo) #4474
• port message sign to master-n3 neo-node#924

[shargon]

Meeting Summary - 2026-02-05

Attendees: cschuchardt88, Alvaro Jara, Vitor Nazário, Anna Shaleva, Fernando Díaz, Roman Khimov, Jimmy Van, xiaolubao9, Erik Zhang.

1. [N4] Adapt neo-node to Neo 4.0.0 (neo-node#989)

• Status: In progress.
• Agreement: Alvaro confirmed that work is ongoing to fix the master build issues which are currently causing PR failures. The goal is to have this PR finished by next week.
• Core Vision: Jimmy clarified that Neo 4 should maintain 100% codebase compatibility with Neo 3 to avoid migration issues, essentially acting as a version upgrade that enables multi-chain/sidechain capabilities.

2. Proposal: Remove Voting Rewards and Introduce Native Staking Rewards (#4467)

• Agreement: Given the complexity and impact on Neo 3 economics, it was proposed to merge the staking changes into Neo 4 first.
• Rationale: This allows for a quicker implementation in a "new" environment while continuing the discussion for a feasible, potentially less radical solution for Neo 3 (such as flattening voter rewards instead of full staking).

3. [N3] Port 4318 fixes: VerifySignature, VerifyWithEd25519 and VerifyWithECDsa (#4449)

• Agreement: Fernando emphasized the need for caution when porting these logic changes to Neo 3, specifically ensuring that hard fork logic is correctly implemented to maintain chain integrity.

4. dNeo (Decimal Neo) / bNEO Deprecation (#4474)

• Agreement: The team decided against a native contract solution to avoid complexity.
• Action Plan: Fernando will coordinate with the Flamingo team to maintain a new, non-native token with decimals to replace the deprecated bNEO contract. Jimmy suggested that a quick fix would be deploying a copy of the old bNEO contract under a new name/address.

5. Port message sign to master-n3 (neo-node#924)

• Discussion: There is a conflict between maintaining compatibility with existing wallet standards (Neoline/Neon) and addressing replay attack vulnerabilities.
• Outcome: Fernando suggested adding a boolean argument to allow users to opt-in to the older, vulnerable version for compatibility if needed, though Jimmy argued that security-conscious users should include network info in their messages. The discussion was noted as prolonged and requires a final decision on the security vs. compatibility trade-off.