Code3ks retweeted
🔄 DAO Proposal Sync (Discussion Phase)
Project: FiberNuts — Cashu-based RUSD payments over Fiber.
Applicant: Code3ks.
Previous work: The applicant reports an existing adapter, browser wallet, and live public-testnet Community Market.
Deliverable: A 12-week programme covering settlement and refund recovery, public-testnet onboarding through a hosted LSP so users need not run a Fiber node, reusable releases, an upstream contribution, independent validation, and a Community Market pilot.
Budget: $6,000 USD equivalent, paid in CKB at the exchange rate at each disbursement. Four equal $1,500 instalments: 25% on approval, then 25% after acceptance of each milestone at weeks 4, 8, and 12.
Scope: The mint remains custodial. Mainnet validation is limited and subject to safety checks. Public mainnet launch, a formal audit, and grant-funded reserves or channel liquidity are excluded.
30 likes on the first post within seven days makes the proposal eligible to proceed to the Voting Stage after the discussion period.
👉 talk.nervos.org/t/11051
Check out my proposal here: talk.nervos.org/t/dis-fibern…
🔄 DAO Proposal Sync (Discussion Phase)
Project: FiberNuts — Cashu-based RUSD payments over Fiber.
Applicant: Code3ks.
Previous work: The applicant reports an existing adapter, browser wallet, and live public-testnet Community Market.
Deliverable: A 12-week programme covering settlement and refund recovery, public-testnet onboarding through a hosted LSP so users need not run a Fiber node, reusable releases, an upstream contribution, independent validation, and a Community Market pilot.
Budget: $6,000 USD equivalent, paid in CKB at the exchange rate at each disbursement. Four equal $1,500 instalments: 25% on approval, then 25% after acceptance of each milestone at weeks 4, 8, and 12.
Scope: The mint remains custodial. Mainnet validation is limited and subject to safety checks. Public mainnet launch, a formal audit, and grant-funded reserves or channel liquidity are excluded.
30 likes on the first post within seven days makes the proposal eligible to proceed to the Voting Stage after the discussion period.
👉 talk.nervos.org/t/11051
My FiberNuts grant proposal is live on Nervos Talk!
Building reliable Cashu-over-Fiber payments with hosted LSP onboarding.
CKB community, check it out, drop a like , and share your feedback!
🔗 talk.nervos.org/t/dis-fibern…
Hey everyone, I’ve shared an update on FiberNuts Community Market, which is now open for public testing on CKB Testnet.
Forum update: talk.nervos.org/t/fibernuts-…
Demo: market.fibernuts.xyz
Check it out and drop a feedback. Thanks.
Pocket Node @PocketNodeCKB just got better,
Better security,
Better UI
Code3ks retweeted
I am not saying its the coolest tool out there, but its getting preety close to it! Are there CKB fans out there that wanna participate in awesomness? Come say hi
web.telegram.org/a/#-1004457…
talk.nervos.org/t/cellula-wa…
Open source your mind, this is where we begin!
My FiberNuts grant proposal is live on Nervos Talk!
Building reliable Cashu-over-Fiber payments with hosted LSP onboarding.
CKB community, check it out, drop a like , and share your feedback!
🔗 talk.nervos.org/t/dis-fibern…
Hey everyone, I’ve shared an update on FiberNuts Community Market, which is now open for public testing on CKB Testnet.
Forum update: talk.nervos.org/t/fibernuts-…
Demo: market.fibernuts.xyz
Check it out and drop a feedback. Thanks.
Thank you @FiberDevs
Community feedback provides great value, because it helps me to improve and harden FiberNuts protocol.
Nice to see more Fiber projects moving from prototypes to public testing!
@ebubedev opened Twine's P2P trading app for testnet testing, @Code3ks opened the FiberNuts Community Market (and already shipped fixes based on feedback), and @truthixifi turned hackathon feedback into Fiber Forge v0.4.0, with new SDK, CI, and CCH testing tools.
Meanwhile, @Dean8IX shared new recovery evidence for FNN Safeguard, and @LusoCryptoLabs opened the Cellula Wallet testnet beta.
If you're trying out any of these projects, let the builders know what works or breaks, and what you'd like to see next!⚡
Catch up with the community in Pulse 17: fiber.world/blog/pulse/issue…
Code3ks retweeted
Blackbox Devlog #10: prepaid card and tap-to-pay support added
Prepaid card support:
- A tap reads the card’s balance and counter, checks whether the sale is allowed, writes the new balance back, and signs the result; no server, no live transaction
- The terminal holds a debit key that can spend down a card but cannot create value; issuing and loading stay in the Vault, which holds the on-chain reserve behind each card
- Settlement is a separate, later act: the terminal journals every completed tap and batches them to the Vault when it can; until then it runs on an unsettled cap, bounding the worst case of a terminal that never phones home
- Currently a demo tier running on cheap NTAG cards with a custom MAC rather than the DESFire EV3 secure element the shipping card will use; disabled by default behind a compile-time flag
Handling failed taps:
- Every debit is written to a journal as an intent before the card is touched, removed only once the card write is confirmed; a card pulled mid-write, a power loss, a reader glitch each land in a state the terminal can name and recover from
- A write known not to have landed charges nothing; a write whose outcome is unknown parks until the same card is tapped again, resolving to exactly one charge or none
- Cards were yanked mid-write deliberately five times at the bench; the ledger came out with five charges, no doubles, no losses
- A sale cancelled at the instant of card write raises a flag the cashier must acknowledge, and the same card is refused a second tap until they do; the guard is held until cleared, not on a timer
Vouchers and staff keys:
- Item vouchers put a product rather than a balance on a tag, each backed by a chain cell that closes automatically once settlement lands
- Staff keys use the cryptographic originality signature NXP puts on genuine NTAG silicon; a price override requires a staff tag. The demo cards turned out to be counterfeit and cannot produce this signature, which is precisely why staff authorisation uses it
Bug: UI freeze under concurrent flash writes:
- The confirmation screen began freezing hard after a successful card debit followed immediately by a settlement sync
- Cause: an SPI flash write on the ESP32-S3 briefly stalls the other CPU core; the journal task was unpinned, so it ran on the core opposite the UI, dropping the UI’s clock tick mid-sleep
- Fix: pin flash-writing tasks to the same core as the UI, so the stall lands on the networking core; seventeen hours of uptime and a full bench run with no recurrence. The same latent bug was found and fixed in the Bitcoin header path before it surfaced
Also:
Add Item form now has a Scan barcode button that arms the scanner in place and drops the code into the field, keeping name and price already typed
Space bar on the Add Item keyboard was hidden under the footer bar; fixed
Next: watchdog for a genuinely wedged terminal, certificate pinning so settlement cannot be spoofed on a hostile network, on-device voucher and staff key support, and the DESFire secure-element card once stock arrives.
Full devlog: blackbox.wyltekindustries.co…
Hey everyone, I’ve shared an update on FiberNuts Community Market, which is now open for public testing on CKB Testnet.
Forum update: talk.nervos.org/t/fibernuts-…
Demo: market.fibernuts.xyz
Check it out and drop a feedback. Thanks.
Update: you can claim tesnet RUSD to test the community market app on fibernut
It’s also my birthday :
Link 👇
Code3ks retweeted
Another reason to avoid relying on an ever-growing list of cryptographic precompiles is that each one embeds a cryptographic operation in the protocol’s consensus rules.
Introducing a new signature scheme this way requires the network to reach social consensus around a fork.
There is a consistent direction in Vitalik’s proposals, from exploring RISC-V as a replacement for the EVM to now advocating “EIP-8288 maximalism”: give Ethereum room to support new cryptography without continually expanding the protocol.
EIP-8288 would open a path to supporting different signature schemes without a dedicated precompile for each. Signature verification would be proven off-chain, and those proofs aggregated for the chain to check, reducing the associated data and verification costs.
The broader idea is one we've discussed extensively: blockchains are for verification, not computation. Vitalik is reframing the "world computer" along precisely these lines: "any data/computation that does not need to be in the 'main thread' of data/execution should not be put into the main thread."
This is the reasoning CKB was built around from the beginning. Its accounting model (the Cell model, which is a generalized version of the UTXO model) separates off-chain state generation from on-chain verification.
CKB also launched without cryptographic precompiles. Signature verification runs as ordinary software on its RISC-V VM, so developers can introduce new schemes as Lock Scripts and users can adopt them without waiting for a protocol upgrade. That's how an audited post-quantum lock, SPHINCS+, is already live on mainnet.
The idea is simple: keep the base layer simple and stable while giving the cryptography and applications built on it room to evolve.
It's the essence of crypto-agility, and it's becoming more appreciated amid the looming threat of cryptographically relevant quantum computers and AI.
Ultimately, precompiles and EVM are both the wrong place to put most cryptography support into Ethereum. The reason is that precompiles and EVM both operate on data that has to be included into the ethereum chain somehow, which realistically means included in a block as calldata. That space is limited - even with PeerDAS and blocks-in-blobs, there's a practical cap of ~8 MB/s before it starts getting uncomfortable.
Remember: it's not a blockchain. It's a cryptographic world computer. Any data/computation that does not need to be in the "main thread" of data/execution should not be put into the main thread.
Instead, the correct solution is... EIP-8288 maximalism.
If you have any heavy computation that's self-contained, compute it and STARK it client-side (this is quickly getting faster and faster, even on phones), and push the STARK through the EIP-8288 recursive aggregation mechanism. The chain sees the fact that the computation was done and what the result is; it never needs to see the actual data and computation.
This way everyone can use whatever cryptography they want, the Ethereum chain can be lean, and we never need to add more precompiles again.
Code3ks retweeted
The CKB community is growing from strength to strength. Q3 saw more community developer participation than ever before, a hackathon, a ton of dev meetups, and so much more!
Read more about it here:
talk.nervos.org/t/nervos-com…



















