jay zhou

peace and love

[jay zhou @ronment3]

@michaelsuttonil Thanks

[Michael Sutton @michaelsuttonil]

pre-release: https://t.co/XQZSof2d0y

discord: https://t.co/gMvUmNdbI5

pub rnd: https://t.co/2VLrnspT3Z

[Michael Sutton @michaelsuttonil]

Kaspa Toccata mainnet process update:

Today we plan to publish the v1.3.0 mainnet pre-release, without activation, for 1–2 days of broader network sanity testing.

Assuming everything looks good, the following release will be v2.0.0, with activation planned for June 30, 4 weeks from today

[jay zhou @ronment3]

@AppKaskad @DefiLlama @Igra_Labs Excuse,There are only 0.8M USDC and 0.15M USDT on the entire chain. Even if all of them were staked here, the TVL would far exceed the total on the entire chain. What could be the reason for this?

[jay zhou @ronment3]

@Kaspa_KEF @oneforonehaha RTD is coming

[jay zhou @ronment3]

@CryptoBabyCN KCC20 L1 coming ,krc20 L2, kasplex zkevm L2,igra L2

[jay zhou @ronment3]

@KasTipApp Thanks

[Kastip @KasTipApp]

4/ Transparency matters.

KaSTip is open source:
https://t.co/mlRVkZ7E2I

Privacy policy:
https://t.co/6xu7MkpVFa

Crypto users should be curious and cautious. That's a good thing.

Install link is in bio / pinned post.

[jay zhou @ronment3]

@manyfest_ Excuse ,can you share the node you finded? what's the way the find a public TN10 node?Thanks

[jay zhou @ronment3]

@manyfest_ Thanks,it works well ,now TN10 update TOC3

[jay zhou @ronment3]

@manyfest_ Thanks

[Manyfest @manyfest_]

One cool thing about such simple contracts is that we can track their activity on the explorer as if they were a normal wallet address. This is because they have no state, so their script/lock always stays the same, no matter the amount of KAS they hold in the UTXO.

I created another small app that calculates the contract address on mainnet or TN10.

The contract you see in the app is the latest KasPot contract, you can also paste the contract below to compile an earlier version I toyed with and examine its activity on the tn10 explorer.

P.S. The app uses a WASM compilation of the SilverScript compiler, so the source is compiled directly in the browser. Thanks Codex!

https://t.co/NIQBvAqjxZ

Earlier prototype to paste into the app:

pragma silverscript ^0.1.0;

contract Faucet() {
int constant CLAIM_COOLDOWN = 600;
int constant MIN_FUND_AMOUNT = 1 kas;
int constant MAX_CLAIM_AMOUNT = 1 kas;
int constant MAX_MINER_FEE = 10 grains;
int constant MAX_SPEND = MAX_CLAIM_AMOUNT + MAX_MINER_FEE;
int constant FAUCET_OUT_INDEX = 0;

function selfPreserve() {
byte[] selfScriptPubKey = tx.inputs[this.activeInputIndex].scriptPubKey;
require(tx.outputs[FAUCET_OUT_INDEX].scriptPubKey == selfScriptPubKey);
}

entrypoint function fund() {
selfPreserve();
int nextValue = tx.outputs[FAUCET_OUT_INDEX].value;
int prevValue = tx.inputs[this.activeInputIndex].value;
require(nextValue - prevValue >= MIN_FUND_AMOUNT);
}

entrypoint function spend() {
require(this.age >= CLAIM_COOLDOWN);
int prevValue = tx.inputs[this.activeInputIndex].value;
bool allowEmptying = prevValue <= MAX_SPEND;
if (!allowEmptying) {
selfPreserve();
int nextValue = tx.outputs[FAUCET_OUT_INDEX].value;
require(prevValue - nextValue <= MAX_SPEND);
}
}
}

[KasMap @KasMaporg]

#MyKAI has about 50 nodes running on a daily base, of which 40ish nodes are running simultaneously.
Keep spreading the word to help #Kaspa be really decentralized 🌎🌍🌏

And if you havent done so yet, give it a try &amp; start running a MyKAI node yourself.
Work for your $KAS 😜

[jay zhou @ronment3]

@BankQuote Thanks

[BaN𐤊ℚuOτE @BankQuote]

I built OpenSilver because Kaspa’s covenant ecosystem is going to need more than theory.

It is going to need open-source tooling, reusable patterns, public review, and a development surface that builders can actually understand without starting from zero every time.

OpenSilver is an open-source toolkit for building covenant-based applications on Kaspa. For non-technical people, think of it like a public library of reusable “rules for money.” Instead of an app needing a company, custodian, or middleman to decide when funds move, a covenant can lock KAS inside a transaction with conditions attached. Funds can release after a deadline, require multiple approvals, stream over time, recover through backup keys, execute escrow logic, support swaps, or interact with verification systems. OpenSilver collects these kinds of patterns into one shared library so builders can use, inspect, improve, and standardize them in public.

For developers, the important part is that OpenSilver is not trying to turn Kaspa into an Ethereum clone. It is built around Kaspa’s UTXO model and SilverScript covenant logic, meaning enforcement happens through transaction constraints rather than a global account-based smart contract VM. The repo includes patterns for ownership, multisig, timelocks, vaults, escrow, vesting, dead man switches, social recovery, HTLC-style atomic swaps, streaming payments, payroll and freelance flows, token-related KRC patterns, and early ZK-aware structures. The goal is to make Kaspa’s post-Toccata programmable surface easier to reason about, test, reuse, and integrate.

The open-source angle is the real point. If Kaspa covenants are going to become serious infrastructure, developers need shared primitives, examples, manifests, CLI tooling, runtime checks, walkthroughs, and public review. Otherwise the ecosystem fragments into isolated scripts, duplicated logic, and avoidable security mistakes. OpenSilver gives builders a common foundation while letting the community audit the logic in the open before serious value depends on it.

It is still early. These patterns are not externally audited yet, and some advanced ZK-facing pieces depend on upstream SilverScript and protocol maturity. But that is exactly why I built it in the open.

OpenSilver is not just code.

It is scaffolding for a native Kaspa application layer.

https://t.co/qCL2BfuWP5

[jay zhou @ronment3]

@KasMaporg I need it ,thanks

[jay zhou @ronment3]

@KasMaporg Thank you for your work. I have a small suggestion: version 1.1.0 is intended for the mainnet, whereas Toccata has already been implemented in TN10. The corresponding branch is 1.2.0; therefore, please upgrade kaspad to version 1.2.0.