Log inSign up
Steven Roose
Second
6,049 posts
user avatar
Steven Roose
Second
@stevenroose3
Libertarian socialist bitcoiner; believe it or not. Building Ark as CEO @secondhq, opinions obviously my own. KYC is the crime.
roose.io
Joined December 2010
1,178
Following
2,030
Followers
  • Pinned
    user avatar
    Steven Roose
    Second
    @stevenroose3
    Aug 26, 2025
    I don't hold bitcoin for maximum "profits". I hold bitcoin for peace-of-mind. No need to deal with banks and risk temporary confiscation. It's apolitical. It's entirely peaceful (unlike the stock market or landlording). It's super secure but still practical to move.
    user avatar
    WhalePanda
    @WhalePanda
    Aug 25, 2025
    If it was the cycle top, which I don't think it was, there is no reason to hold BTC as store of value. Why would I hold something that loses 80% of its value? "Bitcoin went from 16k to 124k" No. Bitcoin went from 69k to 124k in 4 years. Plenty of assets did better.
    Image
    7.5K
  • user avatar
    Steven Roose
    Second
    @stevenroose3
    Oct 31, 2019
    11 years ago today #Bitcoin #SatoshiNakamoto #Whitepaper
    Image
  • user avatar
    Steven Roose
    Second
    @stevenroose3
    May 27, 2025
    Casually followed the Las Vegas stream today. This must have been the most bearish bitcoin conference day I've known. Almost every person on stage was either a corporarist or a member of government. Anyone 'member what bitcoin is supposed to be about?
    19K
  • user avatar
    Steven Roose
    Second
    @stevenroose3
    Jan 16, 2020
    Last words on Twitter of early Bitcoin developer Tamas Blummer who recently passed away. Having been requested so in the week before his passing, I'm committed to continue the work on some of his Bitcoin projects! Especially Murmel and DefiAds are very interesting. R.I.P.
    user avatar
    Tamas Blummer
    @TamasBlummer
    Jan 3, 2020
    Happy birthday bitcoin. It has been exciting and enriching working for you for many years.
  • user avatar
    Steven Roose
    Second
    @stevenroose3
    Apr 30, 2025
    On the OP_RETURN drama, what actually triggered this is the BitVM folks about to launch a protocol that needs to commit ~100 bytes of data and the current OP_RETURN limit being too restricted for that. So they "fixed" that by committing the leftover bytes in p2tr outouts.
    27K
  • user avatar
    Steven Roose
    Second
    @stevenroose3
    Dec 15, 2018
    Andrew Poelstra on new cryptographic ideas like Schnorr signatures, #bulletproofs, #taproot and the future of #Bitcoin development! youtu.be/jWAhDH07bUY
  • user avatar
    Steven Roose
    Second
    @stevenroose3
    Feb 22, 2025
    I think my ideal roadmap looks like this (script-related): - enable CTV and CHECKSIGFROMSTACK asap - Great Script Restoration - upgrade CTV with TXHASH + add some form of direct introspection + ECMUL/TWEAKADD
    33K
  • user avatar
    Steven Roose
    Second
    @stevenroose3
    Mar 12, 2025
    For the sake of the argument, I tried to see how hard it would be to port our Ark implementation to CTV. It took literally just a few hours to get it entirely working: codeberg.org/ark-bitcoin/ba… Disclaimer: the code is incredibly ugly because it's doing conditional compilation
    13K
  • user avatar
    Steven Roose
    Second
    @stevenroose3
    May 8, 2025
    I haven't heard anyone say that jpegs on the blockchain are good though. Neither that OP_RETURN data is good. Who mais that claim? The claim is that it's worse if they are consensus legal but not relayed, cuz it will lead to miner centralization.
    user avatar
    Joyce Dawn
    @BitcoinWifey
    May 8, 2025
    Beautiful @GrassFedBitcoin 🙏
    Image
    00:00
    6.9K
  • user avatar
    Steven Roose
    Second
    @stevenroose3
    Apr 30, 2025
    Replying to @stevenroose3
    This would create p2tr outputs that are unspendable and will live forever in all nodes' UTXO sets. This is actually a negative for bitcoin's long-term viability, so increasing the OP_RETURN limit here is actually a positive. The bikeshed is what the new limit should be.
    2.1K
  • user avatar
    Steven Roose
    Second
    @stevenroose3
    Apr 13, 2025
    OP_NEXT was an absolute banger!
    user avatar
    Neil Woodfine
    Second
    @nwoodfine
    Apr 13, 2025
    All reports suggesting OP_NEXT was a great event.
    13K
  • user avatar
    Steven Roose
    Second
    @stevenroose3
    Jan 14, 2025
    A tonsilitis and a flu made me miss my goal by two weeks, but finally finished a revised version of the TXHASH BIP: github.com/bitcoin/bips/p… Special thanks to @reardencode for co-authoring some of the new changes!
    Image
    BIP346: OP_TXHASH by stevenroose · Pull Request #1500 · bitcoin/bips
    From github.com
    6.6K
  • user avatar
    Steven Roose
    Second
    @stevenroose3
    Aug 29, 2025
    It's been about one year since we founded our company Second (@secondhq) to build the Ark protocol for bitcoin. It's been a busy year! Our team has grown to 7 full-time members and I couldn't be more proud of them! We built a lot, but we have a lot more to build! Stay tuned! 🔥
    Image
    7.2K
  • user avatar
    Steven Roose
    Second
    @stevenroose3
    Apr 30, 2025
    Replying to @stevenroose3
    It feels wrong to just increase it enough to accommodate BitVM. Both because we shouldn't play favorites, but also because the next protocol requiring more data will again start using other outputs, again causing a negative effect. So why not remove the limit entirely?
    2K

New to X?

Sign up now to get your own personalized timeline!

Create account

By signing up, you agree to the Terms of Service and Privacy Policy, including Cookie Use.

Terms·Privacy·Cookies·Accessibility·Ads Info·© 2026 X Corp.
Don't miss what's happening
People on X are the first to know.
Log inSign up
Advertisement
Advertisement