Live data from Hacker News

Viewing profile — mriou

mriou

HN member
Joined
Wed, Aug 22, 2012, 8:47 PM UTC
HN karma
51
Public activity
29 items

About mriou

http://www.blockcypher.com http://www.offthelip.org

Recent public activity

  1. story
  2. comment
    Comment #10153214

    BlockCypher | SF Bay Area (Redwood City) | onsite We're building a block chain platform. We have web services to make it easy and quick for people to start developing for bitcoin a…

  3. story
  4. story
  5. story
  6. story
  7. comment
    Comment #8070650

    To support Urea we mostly had to add support for the X11 hash function and implement the Kimoto Gravity Well algorithm: http://bitcoin.stackexchange.com/questions/21730/how-does-th…

  8. comment
    Comment #7972622

    Will do, thanks a lot for the feedback.

  9. comment
    Comment #7972473

    It is non-trivial to create and sign a transaction among multiple parties. The point of multisig is that you have several entities, some can be humans, some can be machines, progra…

  10. comment
    Comment #7972433

    Thanks for the feedback, we will add a section on how to verify it.

  11. comment
    Comment #7972132

    Not blindly, you see both the generated transaction and the data to sign, you can validate either or both. And you are completely trusting a server in many other situations.

  12. comment
    Comment #7971704

    This is incorrect. You can have servers using multisig too, it increases the overall security of the transactions, especially if the different private keys are stored in different …

  13. story
  14. comment
    Comment #7663610

    They have. But only if you're on node.js and you need to run bitcoind yourself. Which means maintaining it, backups, restart scripts, etc. Building the transaction using BitCore is…

  15. comment
    Comment #7662821

    It's much simpler than it sounds, only 7 lines of code in the sample posted. The point is that most people don't want to share their private key or their users' private keys, justi…

  16. comment
    Comment #7662721

    The full API documentation can be found there: http://dev.blockcypher.com/ Includes websockets and webhooks to get notified on a variety of blockchain events.

  17. comment
    Comment #7622243

    Not sure how well-maintained it is but: http://www.scalajobz.com/

  18. comment
    Comment #7560762

    Our APIs will expand a lot over the coming months. Any feedback on people see as most useful is highly valuable.

  19. comment
    Comment #7543333

    Banks are made of a mess of different systems. Some are locally ACID, but overall reconciliation and compensation are what keeps it all together. Regardless, this has little to do …

  20. comment
    Comment #7510163

    I'd be curious to have your perspective on the risks of relying on 3rd party infrastructure. That 3rd party can't really try to feed wrong blocks or transactions, it would ruin its…

  21. comment
    Comment #7494271

    I'm really glad Andreas is writing this book, should be a great way for more developers to get involved. Crypto-currencies are unfortunately still a little too arcane and books lik…

  22. comment
    Comment #7483352

    > you can still feel pretty safe with 0 confirmations if you're monitoring the > bitcoin network for double-spend attempts over the average network propagation time The above is mu…

  23. comment
    Comment #7433046

    Fair point. The original argument was advocating non-fractional though.

  24. comment
    Comment #7432956

    And it happened even only with bitcoin-core. Anyhow the 50/50% scenario across implementations is unlikely to happen if everyone seeing a new one cries forking wolf. I do empathize…

  25. comment
    Comment #7432809

    I've heard that argument many times and all it does is reinforce the idea that no other implementation can work. And how you end-up with an implementation mono-culture. Forks of a …