eric

2.2K posts

eric banner
eric

eric

@ECBSJ

Forward Deployed DevRel

Katılım Temmuz 2019
894 Takip Edilen1K Takipçiler
eric
eric@ECBSJ·
@fakfakfun bullish on all honest forms of development in the Bitcoin eco
English
1
0
3
132
FakFun
FakFun@fakfakfun·
if eric is building on bob it makes me bullish for bob - simple maths
eric@ECBSJ

using @build_on_bob Gateway CLI with @OpenWallet is a wicked combo for agentic bitcoin payments check out my previous tweet for the full demo

English
2
2
4
152
eric
eric@ECBSJ·
using @build_on_bob Gateway CLI with @OpenWallet is a wicked combo for agentic bitcoin payments check out my previous tweet for the full demo
English
1
3
13
685
Nikki Sunset
Nikki Sunset@nikki_sunset·
This builder leveraged the BOB Gateway CLI to make an inscription on Bitcoin via a governance contract on Ethereum, trustlessly. BOB Gateway lets EVM devs interact with Bitcoin in the simplest way. Link to @dom60808 's original blog post on this specific use case: gobob.xyz/en/blog/trustl…
eric@ECBSJ

Governed on EVM. Inscribed on Bitcoin. Trustless Bitcoin inscriptions approved by a DAO and funded cross-chain through the @build_on_bob Gateway CLI. What's the inscription I commit/reveal in the demo? “We're embracing inclusivity over maximalism” - @alexeiZamyatin

English
2
2
10
998
eric retweetledi
alexei
alexei@alexeiZamyatin·
Cool use of BOB Gateway CLI: DAOs making inscriptions on Bitcoin, triggered and executed cross-chain. What this means: DAOs / multisigs / contracts on Ethereum can trigger transactions / payments / inscriptions / advanced actions on Bitcoin - without dealing with Bitcoin fees or wallets.
eric@ECBSJ

Governed on EVM. Inscribed on Bitcoin. Trustless Bitcoin inscriptions approved by a DAO and funded cross-chain through the @build_on_bob Gateway CLI. What's the inscription I commit/reveal in the demo? “We're embracing inclusivity over maximalism” - @alexeiZamyatin

English
2
3
16
1.9K
eric
eric@ECBSJ·
Governed on EVM. Inscribed on Bitcoin. Trustless Bitcoin inscriptions approved by a DAO and funded cross-chain through the @build_on_bob Gateway CLI. What's the inscription I commit/reveal in the demo? “We're embracing inclusivity over maximalism” - @alexeiZamyatin
English
4
6
20
3.6K
LabSTX
LabSTX@labstxorg·
@ECBSJ @stackslabs @StacksDevs Love this. We’re planning to build interactive wizards for Clarity 6 right when it launches. Down for a cross-stream to align on this when added with @StacksDevs? 🤝
English
1
0
3
42
LabSTX
LabSTX@labstxorg·
@ECBSJ @stackslabs @StacksDevs Thanks for this! Totally agree—interactive wizards walking devs through those Hiro templates would be a game-changer for onboarding. Def going to look into this. If you have any specific ideas for what the first wizard should cover or perharps other features, let me know!
English
1
0
3
44
eric
eric@ECBSJ·
i've always been a fan of IDEs for smart contract learning. if you're able to integrate mini tutorial wizards navigating through contract templates that'd be solid. the Hiro Platform already has a good base for contract templates and devnet hosting but lacks in interactive wizards
English
1
0
2
58
eric
eric@ECBSJ·
a fair two-sided breakdown of agentic payments and where its headed. a quote that is worth a double take on: "Expect the first major agent-payment liability dispute to shape this layer more than any spec will."
GOAT Network@GOATNetwork

Agent payments crossed 165 million transactions this year, but still represent only a tiny fraction of stablecoin volume. x402 activity peaked near 731,000 transactions a day in December, inflated by memecoin experiments, then fell more than 90% by February. This data is not negative. It proves the rails work, the liquidity exists, and the industry is still early enough to get the stack right before real volume appears. Agent payments and identity are beginning to converge. Settlement has not. Settlement is the point past which a transfer cannot be reversed, frozen, or renegotiated by anyone, including the operator of the system it ran on. Today, that layer is inherited by default from whichever chain a given SDK happens to point at. Those defaults will harden into the architecture trillions of dollars eventually flow through. A settlement layer with an owner can be pressured. The one that cannot is the most neutral, most attack-costly ledger that exists: no issuer, no foundation, no upgrade key, no council. Seventeen years. No rollback. Secured by physical energy, not anyone’s promise. Being early is the chance to build around that base layer before the agents are really adopted at scale. If it doesn’t settle on Bitcoin, it doesn’t settle at all. goat.network/news/a-truthfu…

English
1
0
2
196
GOAT Network
GOAT Network@GOATNetwork·
When @bxHyperMove joined the GOAT AI Builder Grants Program, it brought not only infrastructure that lets AI agents pay for APIs with Bitcoin as collateral - without ever touching a private key - but also a working app already built on it: @0xkinetic10. This is exactly what the program is looking for: builders enabling something new and useful for the GOAT Network community. goat.network/news/meet-hype…
English
97
65
106
195.6K
dominik.btc
dominik.btc@dominik_btc·
Not even gonna pretend I’m a real knicks fan, especially after they let @jlin7 go. But somehow seeing @nyknicks win a chip after 53 years, against a monster like Wemby, still make me linsanely happy. Congrats Knicks, unreal!
dominik.btc tweet media
English
2
0
5
399
eric
eric@ECBSJ·
@botanix sad to hear of such an announcement from a Bitcoin L2 play but unfortunately it does look like Ethereum, in such an ironic and poetic manner, defaults to the Bitcoin L2 noone realized
eric tweet media
English
0
0
1
209
Botanix 🕷️
Botanix 🕷️@botanix·
It is with a heavy heart that we announce we are winding down the Botanix network. This decision is the hardest one we have made in four years, and we want to share the reasoning openly because the people who backed us, built with us, and used what we shipped deserve more than a quiet shutdown notice. First off, an immediate practical consideration for the Botanix community: please withdraw your Bitcoin and other assets before July 9th, 2026. When we started in 2022, the pitch was simple enough to say in a sentence: bring real utility to Bitcoin. What that actually meant in practice, and what we have spent nearly four years building toward, was more ambitious than that sentence made it sound. We were trying to build a Bitcoin-based blockchain that could find genuine product-market fit as a platform for Bitcoin applications, without using token incentives to drive growth, manufacture users, or simulate utility. Almost every chain that has launched in the last cycle has reached for the same playbook (issue a token without PMF, engineer the incentive surface, point at the resulting metrics), and we did not believe this route is a viable strategy in the long term. We wanted to know whether a Bitcoin chain could earn its users on the strength of what was built on top of it, the value it brings in the market with Bitcoin itself as the only meaningful economic primitive in the system. And we built it. The Spiderchain went live and stayed live, a year of mainnet operation with one hundred percent uptime and zero security incidents on a genuinely novel cryptographic architecture. We built Dynafed, a dynamic federation that turned the Spiderchain from a static multisig set into a rotating, decentralized one, the technical milestone that most people in this space said could not be built on Bitcoin without compromising trust assumptions. Twenty-five million transactions, two hundred thousand wallets, and tens of millions of dollars in assets moved across the chain, every single number of that earned organically without a token, without airdrops, without points programs, or any of the manufactured-demand machinery. Chainlink, Morpho, GMX, Dolomite, Fireblocks, Alchemy, Galaxy, OKX Wallet, all integrated. We shipped a Bitcoin neobank with BINK on iOS and Android, with self-custodial email login for Bitcoin (something that had never existed before), native Bitcoin yield, and the lowest borrowing rates against Bitcoin anywhere in the world, all of it downstream of owning the infrastructure. The point of saying this is not to argue with our own conclusion. The protocol works, the product works, and our team and ecosystem worked in concert to do exceptional work. We have run this experiment in earnest, with a working protocol, real applications, and a serious team, for over a year on mainnet and nearly four years in total. The honest answer we have arrived at, after living inside it every day, is that it did not work, at least not in this market and not on this timeline. We want to share what we think we learned, with the caveat that some of this is conviction and some of this is still suspicion, and we would rather be transparent about the difference than pretend to have clarity we do not have. The first thing I've had to sit with is timing. Bitcoin utility, making Bitcoin programmable, productive, and integrated into real financial activity, isn't where the real world users sit right now. The conversation is still on Bitcoin as a reserve asset, on its monetary and political positioning, on base-layer conservatism. Those questions are upstream of the ones a Bitcoin L2 needs people to be asking. I still believe Bitcoin gets there, but belief in the destination is not the same as being able to predict when, and nobody can. It's also possible the destination never materialises at all, and that Bitcoin's role as a reserve asset is simply where it settles. If that's true, there will never be a market for what we were building, and no amount of time or capital would change that. The second is the token question. We intended to eventually launch a token. We saw it, and still see it, as a genuinely new form of equity, something closer to an IPO than an airdrop, to be done when you reach product market fit and the moment is right. That moment never came. What became clear over the last year is that the market largely stopped rewarding even the more considered versions of that playbook. Token launches across the board have broadly underperformed, and those that did go to market with tokens haven't seen the outcomes or PMF that the model is supposed to produce. The third lesson is about where DeFi demand on Bitcoin actually lives. For most use cases that exist today, lending, yield, leveraged exposure, WBTC on a mature general-purpose L2 is genuinely sufficient. Users have voted with their behaviour, and the verdict is that the trust assumptions of a wrapped representation on Ethereum are acceptable to almost everyone who wants Bitcoin-denominated DeFi. Decentralisation matters to people in principle and in conversation; in practice, when something cheaper and easier is in front of them, they use it. The security case for a dedicated Bitcoin L2 is real, but it only matters for a narrower band of applications than our thesis required, one of the clearer lessons this market has taught us. The fourth lesson is structural. The on-chain economy is consolidating around venues that own the user relationship: Hyperliquid, Robinhood, the major CEXes, and now TradFi participants absorbing an ever-larger share of attention, flow, and revenue. Convenience and institutional credibility win, every time, as soon as they're available. As retail participation thins, that concentration only deepens. We were, and still are, believers in decentralisation, but the current direction of on-chain growth is running through distribution, and any team building base-layer infrastructure today is rowing upstream against that current. We were no exception. The fifth lesson is the most concrete. Both of the above played out directly in our economics. The users we attracted were primarily using Bitcoin as a store of value for yield, a legitimate use case, but not the high-frequency transaction volume that drives fee revenue on a network like ours. BINK was our answer to that: a Bitcoin neobank designed to bring daily usage of BTC and stablecoins on-chain, driving the transaction volume the network needed. It was the right strategic instinct, and one we never got the chance to fully test. BINK only landed on both app stores in the last few weeks, a product that by its nature could only be built once the underlying infrastructure was proven and live. When users choose the convenient option and economic gravity pulls toward distribution, what's left on a decentralised infrastructure layer is a user base that costs more to serve than it generates. Infrastructure costs are what they are, and the fee income never came close to covering them. If you would like to see how we were imagining a Bitcoin future and what we have been working on since September, feel free to download BINK and give it a spin: it’s a full-fledged self-custodial Bitcoin Neobank with email login, one click borrowing, a Lightning integration and more. App store: apps.apple.com/us/app/bink-bi… Play store: play.google.com/store/apps/det… This UX is where we think Bitcoin is ultimately heading towards although it feels too early. You can use invite code 1SD31R, but remember to remove your funds by July 9th. We could keep going. We have chosen not to, however, because continuing past the point where additional time stops producing additional learning is not conviction, it is something that looks like conviction from the outside while corroding into something else on the inside. We would rather stop now, with integrity intact and resources available to take care of the people who took a chance on us, than push the experiment past the point where it still has something to teach us. Reminder: Please withdraw all your assets by July 9th. After this, the federation will sweep the remaining Bitcoin. Any other assets or tokens on the network from then onwards will unfortunately be unrecoverable. After this, the federation will sweep the remaining Bitcoin. Any other assets or tokens on the network from then onwards will unfortunately be unrecoverable. To our investors, who backed a thesis that was harder to defend than it should have been, to our partners who built alongside us and bet pieces of their own roadmaps on ours, to the developers who deployed on Spiderchain, to our users and the BINK community who showed up for something experimental and stayed, and most of all to the Botanix team who shipped a genuinely novel system with rigour and care and who made every hard day worth the difficulty: Thank you, more than the words available here can carry.
English
110
98
428
161.4K
eric
eric@ECBSJ·
Just watched a live demo of the new @MetaMask agent wallet cli I'd be curious now to see how the plumbing of this sizes up with Moonpay's OWS cli Do we foresee an emerging agentic wallet wars on the horizon?
eric tweet media
English
0
0
5
168
eric
eric@ECBSJ·
who else is still on bitcoin stack exchange asking pieter wuille dumb questions? behind every dev there's another dev. @in3rsha shares how the BSE community has been the most helpful in his bitcoin dev journey s/o to all the other helpful OG devs on BSE
English
1
1
8
652
eric
eric@ECBSJ·
who else had a transition from poker to bitcoin? @in3rsha's shares how his web dev skills enabled that crossover to kickstart the educational bitcoin website, Learn Me A Bitcoin. now it's more than just a static site, it's packed with hashing utilities, an explorer, and more
English
0
2
11
782
BitScript
BitScript@bitscriptapp·
@ECBSJ Close but quite! Look closest at the image ;)
English
1
0
1
17
BitScript
BitScript@bitscriptapp·
WHEW! It’s been a while but we’re excited to confirm that you’ll be hearing from us much more frequently as we have a slate of articles, features, & improvements ready to ship. We’ll leave you with a preview of an article ~coming~ soon. Any guesses on what it’s about??
English
2
3
9
896
Alex Miller
Alex Miller@alexlmiller·
Two weeks ago we shared the @Stacks Bitcoin Staking Whitepaper. Today UTXO Management, the asset management arm of $NAKA, one of the largest institutional names in Bitcoin, announced they're deploying into it. They've looked all across Bitcoin and they’re betting on Stacks
stacks.btc@Stacks

BIG news. @UTXOmgmt, the Bitcoin native asset management arm of Nakamoto Inc., is the inaugural participant in Bitcoin Staking on Stacks. This means institutional BTC earning BTC yield, without ever leaving the base layer.

English
19
11
91
4.3K
eric
eric@ECBSJ·
i think we're on different pages here. i wasn't necessarily arguing on the trust assumptions part, but rather more on the sociological/economic front of what i'm seeing play out with current efforts of Bitcoin L2s. i more or less see eye to eye with you on what should constitute as "the only environment where BitVM can actually minimize trust assumptions". no rebuttal there. "Like it or not EVM has been battle-tested 100-1000x more than any other ecosystem." also, your statement here further affirms my take
English
0
0
0
17
David Seroy 🏔️
David Seroy 🏔️@david_seroy·
BitVM is not the issue. Bridging to chains that are not rollups is. The trust assumptions of BitVM are: + 1-of-N honest operators + Honest majority consensus of the destination chain A Bitcoin rollup inherits Bitcoin L1 consensus directly. That’s why it’s the only environment where BitVM can actually minimize trust assumptions. Ethereum, Stacks, and every other external chain have their own consensus systems. Once you bridge to them, you inherit their honest majority assumptions. An honest majority of stakers can absolutely rug and steal from the bridge, period. So “trustless vaults” to Ethereum, or anywhere else, are not actually trustless. They are not better than wBTC or cbBTC and will fail because the market will price in their risk and give them worse financial terms. They are fundamentally incapable of eliminating honest majority trust assumptions because they rely on external consensus. This is not a BitVM limitation. It is a cross-consensus bridging reality. You're also conflating EVM with Ethereum Network. Like it or not EVM has been battle-tested 100-1000x more than any other ecosystem. It has the best tooling, best applications, and best developer experience. The vast majority of recent hacks are human exploits, not EVM ones. -- Further, you can have interoperability across different execution environments with ZK proofs using a single BitVM style bridge.
English
1
0
1
33
eric
eric@ECBSJ·
bitcoin L2s went from providing new application layers tied closely to the L1 to now realizing BitVM can potentially tie the L1 closest to the 2nd biggest honeypot in crypto, ethereum. and you're already seeing this play out with the dozens of “Bitcoin Vault” plays, BTC-backed borrowing for evm assets, and the inheritance of evm toolsets. the sad thing is, there was never any interoperability between the bitcoin L2s nor has there ever been any attempts. it's now becoming a race to see who can export BTC into evm land the fastest and with the least trust assumptions. i'm hyper-postulating here, but I won’t be surprised if BitVM gets us to a place where we mentally default ethereum as the de facto bitcoin L2, coming full circle with it.
bitcoin++ @ toronto, july 22-24 🇨🇦@btcplusplus

JUST SCHEDULED 🏛️: "What happened to Bitcoin Layer 2s" by Talip (@otaliptus) Don't miss it. Join us in Vienna, Austria this May 27+28, 2026 👉 #tickets" target="_blank" rel="nofollow noopener">btcpp.dev/vienna#tickets

English
8
2
19
5.8K
Chase
Chase@prochronist·
@ECBSJ "nor has there ever been any attempts" - @Boltzhq and htlc swaps would like a word
English
1
0
3
81