ixje

> 🔥 burn not migrated tokens. I think it is time to end legacy. @vncoelho the above accounts hold the below number of tokens (migration address not included) ``` Account...

> If these accounts have sent any transactions it's there, witness scripts have verification part corresponding to account. But I understand that it requires some tinkering to get this data,...

> In terms of transparency on the migration from N2 to N3, this has been made clear since the launch of N3. @vncoelho I don't know what you're referring to...

same issue ``` npm ls cross-spawn neon-ts@ /home/erik/code/neon-ts └─┬ [email protected] └─┬ @jest/[email protected] ├─┬ @jest/[email protected] │ └─┬ [email protected] │ └─┬ [email protected] │ └── [email protected] deduped └─┬ [email protected] └─┬ [email protected] └── [email protected]...

As someone who wrote light wallet SDKs, a compliant full node, a standalone indexer/explorer and a bunch of other tools (at [COZ Github](https://github.com/CityOfZion/)) since 2017 I feel we don't need...

> **Encoding Rules:** > > * Implementations **MUST** base64-encode the raw payload bytes as `signedPayloadBase64`. > > * Implementations **SHOULD NOT** include a duplicate hex-encoded payload field; hex can be...

> > https://www.iana.org/assignments/jose/jose.xhtml#web-signature-encryption-algorithms > > We can use the algorithm name listed here. > > Can you please alaborate? I do not understand what part of the proposal you are...

> But I cannot find the Secp256r1 curve listed there, only Secp256k1, which Jimmy told me we do not use: [neo-project/neo#4286 (comment)](https://github.com/neo-project/neo/pull/4286#discussion_r2505936693) Because it's called P-256 in that document I...

I'd like to see a `dynamic` `mode` where `calculateFee` is in the same contract instead of being forced to call an "external" contract. That way it can also be based...