Bitstamp has been marked as "unreachable since 25 Jul, 11:22 UTC" and ignored, but the Bitstamp API appears to be working just fine.
|
|
|
Right now, the above is impossible, because 2 of the co-workers could just sign the transaction without any approval from the boss. What about slightly changing the redeem script so you can define the user & boss keys mandatory, and the 3 co-worker keys optional. Would that be possible?
Scripts are more flexible than just m-of-n. In particular you can use AND and OR to chain m-of-n conditions among other things. User AND Boss AND 1-of-3 coworkers.
|
|
|
It's sold as a way to transfer USD or JPY or BTC or any store of value. It's not.
It is a way to trade IOU's, that rely on your trust in the entity that issued them.
The same is true for wire transfers.
|
|
|
the problem with ripple is you have to make it onto the UNL list, to be part of the consensus.
There's no such thing as the UNL, every node chooses its own UNL. You can't just join.
More precisely, you can't force others to put you on their UNL, since they like you are free to choose their own.
|
|
|
This thread remains a reliable source of people to block.
|
|
|
Merkelised Abstract Syntax Tree. Its root hash gives a summary of the whole AST, just as with a Merkle root in a block. This allows you to give the part of the script that is actually executed when spending, without having to list the whole possibly very lengthy script while still proving you've only used branches from the original AST.
|
|
|
Hi, mmeijeri, have you done anything on this area? any relevant info?
Lots of multisig activity right now. Several groups are working on multisig auctions / ebay clones. Bitrated.com facilitates third party escrow. Virtual-notary.org layers its services on top of the blockchain. Several people have suggested layering distributed storage protocols on top of the blockchain in a way that allows you to store large amounts of data for a fee without bloating the blockchain, while still securing the stored data.
|
|
|
Turns out this patch doesn't work at all, several experts panned it.
|
|
|
pwnt
Heh, I like your grammar. :-)
|
|
|
Bitcoiners actively allow scammers and dreamers, by checking nothing, trusting anything 'because it's Bitcoin' and then accusing any criticism as FUD.
That is changing quickly though and has absolutely nothing to do with Bitcoin itself or even any supposed libertarian philosophy. MtGox was a centralised point of failure in a decentralised system. Centralised exchanges should have no role in a decentralised system.
|
|
|
I'm guessing it's a change of address, but we'll see.
|
|
|
Easy to say that in hindsight.
|
|
|
I do not know more about this case than any random reader of this thread. However, the transition from incompetence to criminality seems to be common in similar situations.
I agree this is a plausible possibility in this case.
|
|
|
So how do "weak minds" cause coins and fiat money to disappear? They don't.
|
|
|
The coins and fiat money didn't disappear because of a "hatred campaign".
|
|
|
Well, that too of course, but 2/3 of the web was vulnerable to this one, whether they updated regularly or not. Layered defence is good.
|
|
|
After the heartbleed scare I've been thinking if perhaps we shouldn't make an effort to store private keys more securely. This isn't a new issue of course, and there are lots of existing techniques and best practices I'm only dimly aware of, including things like PKCS #11 and HSMs. I know work is also being done on Bitcoin-specific hardware solutions like Trezor.
Maybe we all need to move to hardware-based solutions in the future, but maybe there is also room for software-only solutions. Right now most people don't use specialised crypto hardware, and I was wondering if it would help if signing operations were at least located in a separate process with an independent address space. There is a library called SoftHSM which is a software-only implementation of PKCS #11. I think it's supposed to be linked directly to the application, but maybe it can be used as a starting point.
So, what do you think? Would this be a useful near-term improvement, or an undesirable half solution that discourages people from using dedicated hardware, if we believe that's the real solution?
|
|
|
|