niumeta_TZ

3 ms·

1. 1.▲
   A mnemonic-free wallet where the private key never leaves the phone's TEE

   2 points by niumeta_TZ 18d ago|0 comments
2. 2.▲
   by niumeta_TZ 1mo ago

   Existing blockchain architectures simply cannot solve the trilemma – that includes Solana, Hyperledger, etc. They all essentially sacrifice decentralization. Niumeta approaches it from a higher dimension. If we think of traditional blockcha
3. 3.▲
   We tackled the blockchain trilemma with multi‑bucket parallelism (niumeta)(github.com)

   1 points by niumeta_TZ 1mo ago|1 comments
4. 4.▲
   Show HN: A batch settlement layer for tokenized NYSE stocks(github.com)

   3 points by niumeta_TZ 1mo ago|0 comments
5. 5.▲
   by niumeta_TZ 1mo ago

   One thing we're still uncertain about: is SP1 6.2.3's proof generation time (2–3 min on EPYC 7413) acceptable for a production withdrawal system? Would you trust a system with that latency? Curious to hear your thoughts.
6. 6.▲
   by niumeta_TZ 1mo ago

   Author here – adding some context. We're thinking about this at a different level: "Towards a Type I Civilization: A Zero-Trust Network" With the exception of AI training, all traditional data center capabilities can be decen
7. 7.▲
   A ZK withdrawal system without multisig trust(github.com)

   1 points by niumeta_TZ 1mo ago|3 comments
8. 8.▲
   by niumeta_TZ 1mo ago

   We built something that is neither a public chain nor a consortium chain. The goal was to deal with compliance, performance, decentralization and security at the same time. The codebase is very large — 312 Rust crates. Maybe you'll cal