Tweets

You blocked @kanzure

Are you sure you want to view these Tweets? Viewing Tweets won't unblock @kanzure

  1. Pinned Tweet
    Jul 20

    My past ~4 years at have been a blast, and it's time for me to move on:

    Undo
  2. Retweeted
    Sep 23

    Bryan Bishop announces he is a free man after leaving LedgerX earlier this week.

    Undo
  3. Retweeted
    Sep 21
    Replying to and

    I have been developing some content on best practices for both personal (high net worth) & small advisor (<$150M) management of digital assets, which I started when in was at Blockstream. recently architected and deployed an institutional custody system for LedgerX.

    Undo
  4. Retweeted
    Sep 24

    4/ One option would be to, you know, find a way to pay them. Turns out, giving people money is a good way to get them to do hard, highly technical work. Somehow, though, this point is controversial. himself made this clear during that debate:

    Show this thread
    Undo
  5. 10 hours ago

    "Fraud proofs: Maximising light client security and scaling blockchains with dishonest majorities"

    Undo
  6. 10 hours ago

    600 GB corpus of all paywalled pdfs/papers cited on Wikipedia (please torrent) magnet:?xt=urn:btih:f968e22840df243befc6dd123e7d37613002fca8&tr=udp%3A%2F%%3A6969%2Fannounce

    Undo
  7. 11 hours ago

    Bitcoin Core developers have known for years about the kind of high-assurance, formally verified code that bitcoin deserves. One of the problems is that it's profoundly expensive to go and make Coq proofs of everything.

    Undo
  8. Sep 24

    One of 's recent points is that trustlessness is far more easily defined than decentralization. Generally speaking, third parties are third party security holes.

    Undo
  9. Sep 24

    Pushing updates by an aleet system is centralization and an even greater vulnerability. No thank you, Mr. Cobro.

    Undo
  10. Retweeted
    Sep 22

    A third option is 's switch commitments where you can have unconditional privacy, and later use the committed info to upgrade to new key sizes or algorithms ahead of discrete log break on current key sizes.

    Undo
  11. Sep 24

    "Generation of human oogonia from induced pluripotent stem cells in vitro"

    Undo
  12. Retweeted
    Sep 24
    Replying to

    Because he read the notice 😂

    Undo
  13. Sep 23

    Now that Baltic Honeybadger 2018 is over, it's time for and Edge Dev++ in Tokyo.

    Undo
  14. Retweeted
    Sep 23

    11/ Maybe the most interesting institutional event this week was a letter from urging the SEC to treat Bitcoin/crypto in a fundamentally different way, avoiding “commingle” among other things

    Show this thread
    Undo
  15. Retweeted
    Sep 23
    Undo
  16. Retweeted
    Sep 23

    Amazing knowledge dump from a developer who has actually built a successful institutional solution for . Thanks for sharing ! My fave line: "Buy-and-hold should not require a qualified custodian." 100% agreed!

    Show this thread
    Undo
  17. Sep 23
    Undo
  18. Retweeted
    Sep 23

    "Everyone deserves access to a hardware wallet"

    Undo
  19. Retweeted
    Sep 23

    . laying out how partially signed transactions and subsequent deletion of privkey can be used for high-assurance adversarial contexts.

    Undo
  20. Retweeted
    Sep 23

    A company without any bitcoin developers should never act as a bitcoin custodian. Sage advice, but as soon as institutional money is flowing, custodians will quickly outnumber devs IMO... though this will be an important differentiator.

    Undo
  21. Retweeted
    Sep 23

    “You can never have enough checklists”

    Undo

Loading seems to be taking a while.

Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

    You may also like

    ·