人
人
If there are lots of transactions went into the cache pool, sometimes most of them will just stuck in the pool and never finalized, but new transactions seem work well.
Enable the kernel custodian. The key is a threshold multisig custodian between kernel nodes. And kernel nodes change everyday, the custodian can do a new key setup everyday. Another possible...
- [ ] Remove msgpack encoding - [ ] Multiple transactions in a single snapshot - [ ] BLAKE3 as the main hash function
Including mint and node state. This could be done along with the slashing rules.
Since the system is carefully designed to prevent serious incidents like double spending, it's still possible for some nodes to behave incorrectly. The most important one is the node may...
The transaction implementation in BadgerDB is critical for the Kernel consensus, and we can't make the core consensus implementation rely on such a large external project which we have no...
A node may have many keys, a signer key may be BLS or Ed25519, payee key, custodian key, etc.
Now it takes about 1 week to sync a 70GB final snapshots graph.
Mixin Kernel doesn't offer instant total order, but it's possible to get this order from a single node instantly. The node should sign the order along side the snapshot and...
There are plenty of if not something then panic code, refactor them with general functions, but try to avoid reflect.