tap3leaf (🌱) @tap3leaf

covenants/acc @leaf_btc crc.garden google Joined October 2025

Tweets

100
Followers

981
Following

52
Likes

338

tap3leaf (🌱) @tap3leaf

a week ago

(fucking around with that code = oppenheimer vibes.) when u see the vaults the way i see them (unbreachable). u see world finance on bitcoin. for real. being turned (32 bytes) on. (anyway.)

0 9 30 2K 0

View Details

LEAF (🌱) @leaf_btc

3 days ago

"32" is the answer to everything.

26 28 64 5K 3

View Details

tap3leaf (🌱) @tap3leaf

3 days ago

@merklemonkey omg

2 0 5 233 0

View Details

tap3leaf (🌱) @tap3leaf

3 days ago

@merklemonkey @leaf_btc wen

0 0 4 1K 0

View Details

posted on telegram: stay careful with what you click. crc-20 and crc-21 are still in test. (experiments). the team is not in contact with the other builders. their goodwill and professionalism can be real. nobody has come to talk tech yet. mostly people trying to leverage the hype around $leaf. verify the script yourself. (or wait).

0 0 1 137 0

View Details

tap3leaf (🌱) @tap3leaf

5 days ago

@callebtc YES.

0 0 8 546 0

View Details

tap3leaf (🌱) @tap3leaf

5 days ago

great progress on the experiments. first vaults are in test on mainnet. (as ordinal nfts). if it holds for 546 sats (ordinal), it holds for 546 btc. if the tech confirms. (with more btc). that btc can go into the liquidity pools. and from here.. you swap. 🌱

Merkle Monkey (🌱) @merklemonkey

5 days ago

Checkable transfer conditions for Ordinals: a time-locked vault, a state committed through the CMR, and a pre-signed settlement with a fixed input and output. The claim satisfies CRC-21's 32-byte program template. just a proof of the soft-covenant design.

4 7 23 7K 4

22 6 30 4K 2

View Details

tap3leaf (🌱) @tap3leaf

5 days ago

1. the projects you're talking about have nothing to do with $LEAF (or myself). focus here is $LEAF (and koalas). please don't mix the threads. 2. no new soft fork. pre-signed txs + a 32-byte tweak. output locked to that signature. internal key. burned. the 32 bytes match the template or the spend dies. (there is an operator). the kit is checkable when the button is pressed: address, tree, claim, sig. verify before funding. 3. indexer decides and radar observes. (both are useful). about the utxo set and historical scan: study utreexo and floresta.

0 0 5 251 0

View Details

tap3leaf (🌱) @tap3leaf

6 days ago

@BONSonBTC @Bitcoin_Scales @leaf_btc dm

0 0 1 130 0

View Details

tap3leaf (🌱) @tap3leaf

6 days ago

@runes_leo @theprecop @laz1m0v @merklemonkey let's make it clear: i support $leaf (crc-20) and the merkle koalas (crc-21) because they sit on the actual roadmap. (the one activating covenants). the rest: too many unfinished projects floating around. agreed. protocol rules need to go open source. asap.

10 6 24 3K 0

View Details

tap3leaf (🌱) @tap3leaf

6 days ago

if the experiment is unclear: vaults get tested first with a small amount. (that's the only way this gets proven without being stupid). started with an ordinal. 546 sats. cheap. and it shows ordinals can sit under the crc-protocol. nobody has to join this test. sideline is fine. wait. step by step.