mriou

5 ms·

1.
Show HN: Smart Contracts over HTTP(dev.blockcypher.com)
12 points by mriou 10y ago|0 comments
2.
by mriou 11y ago
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 and other cryptocurrencies. We're seed funded ($3M)
3.
BlockCypher raises over $3M to be the Web Services for Cryptocurrency(techcrunch.com)
2 points by mriou 12y ago|0 comments
4.
Is Boost Better Than YC for Bitcoin Startups?(blog.blockcypher.com)
2 points by mriou 12y ago|1 comments
5.
How We Broke the 10 Min Bitcoin Confirmation Barrier(blockcypher.com)
3 points by mriou 12y ago|2 comments
6.
Build a Bitcoin Script Interpreter in JavaScript(blockcypher.com)
2 points by mriou 12y ago|1 comments
7.
by mriou 12y ago
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... The rest (port, block reward,
8.
by mriou 12y ago
Will do, thanks a lot for the feedback.
9.
by mriou 12y ago
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, programming languages can be widely different. And no matter what,
10.
by mriou 12y ago
Thanks for the feedback, we will add a section on how to verify it.
11.
by mriou 12y ago
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.
by mriou 12y ago
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 environments (different datacenters, different OS, etc.). Re
13.
Is Bitcoin security worth $1B?(blockcypher.com)
42 points by mriou 12y ago|31 comments
14.
by mriou 12y ago
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 isn't really simpler either (see the sample https:&
15.
by mriou 12y ago
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, justifiably so. The alternative is building the fu
16.
by mriou 12y ago
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.
by mriou 12y ago
Not sure how well-maintained it is but: http://www.scalajobz.com/
18.
by mriou 12y ago
Our APIs will expand a lot over the coming months. Any feedback on people see as most useful is highly valuable.
19.
by mriou 12y ago
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 with banking. The systems are too widely different to be com
20.
by mriou 12y ago
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 business. Then from a practical standpoint, the o
21.
by mriou 12y ago
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 like these help maturation.
22.
by mriou 12y ago
> 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 much easier said than done. First, you're assu
23.
by mriou 13y ago
Fair point. The original argument was advocating non-fractional though.
24.
by mriou 13y ago
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 with the need of solutions for today though. I was jus
25.
by mriou 13y ago
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 single block happen regularly, it can be dealt with. A
26.
by mriou 13y ago
All great changes, especially BIP 70 and the fixes on transaction malleability and relaying. I'm unconvinced the efforts to make bitcoind (now Bitcoin Core Server) a "border router" are well-spent however. Software that'
27.
by mriou 13y ago
I'm not convinced no fractional reserve is the absolute answer. I am fine with exchanges making some money from what I keep there. In one way or another it will benefit me. What needs to be worked on is the actual fraction they can get
28.
by mriou 13y ago
Bitcoin wallets are surprisingly tricky to implement. Use a good one that a lot of others are using, not the edgy one. Don't try to customize your key pair, just use what's generated for you. Split the wallet you spend from from t
29.
A way for women and minority to make bootstrapping easier(women2.com)
1 points by mriou 14y ago|0 comments