Incentive to spend the Bitcoins / reveal the public key in time

[lclc]

I like the idea, but I see one problem:

The leaker can keep the documents (and the Bitcoin) in hostage until the documents are worthless (he'll still get the Bitcoins).
I can't force him to spend the Bitcoins on that address / reveal his public key.

Do you have a solution for this?

[809894ac]

https://www.mail-archive.com/[email protected]/msg06250.html

If Alice and Bob jointly operate a business they may want to
ensure that all funds are kept in 2-of-2 multisig transaction outputs that
require the co-operation of both parties to spend. However, they recognise that
in exceptional circumstances such as either party getting "hit by a bus" they
need a backup plan to retrieve the funds. So they appoint their lawyer, Lenny,
to act as a third-party.

CHECKLOCKTIMEVERIFY Allows for a third pubkey to spend the coins after X months. This will be part of a future addition, for buyer protection.

[leijurv]

CHECKLOCKTIMEVERIFY has not been implemented yet, and would require a hard fork to implement.

[809894ac]

Without too much thought, what if there was a way to lock the Bitcoins in an address by requiring at least 2x being in the address before being spent.
ex.

Leaker sends 0.5 BTC to chunk X's address
Buyer 1 sends 0.25 BTC to chunk X's address
Buyer 2 sends 0.25 BTC to chunk X's address
chunk X's threshold is reached and coins can be spent

This allows the leaker to recover his escrow (0.5) plus sets a minimum on the buy price, similar to an auction.

[petertodd]

@leijurv CHECKLOCKTIMEVERIFY has not been implemented yet, and would require a hard fork to implement.

It requires a soft-fork to implement, not a hard-fork.

[btcdrak]

Just run DarkLeaks on Viacoin blockchain which already implements CHECKLOCKTIMEVERIFY.

[0kino7ori]

Without too much thought, what if there was a way to lock the Bitcoins in an address by requiring at least 2x being in the address before being spent.
ex.
Leaker sends 0.5 BTC to chunk X's address
Buyer 1 sends 0.25 BTC to chunk X's address
Buyer 2 sends 0.25 BTC to chunk X's address
chunk X's threshold is reached and coins can be spent
This allows the leaker to recover his escrow (0.5) plus sets a minimum on the buy price, similar to an auction.

@809894ac - Interesting concept. I suppose a trusted oracle (darkleaks itself?) would be necessary to check the address balance and return the missing multisig signature to the leaker. Leaker assembles and broadcasts the spending transaction.

But what if the target amount is never reached?

[HostFat]

Any news on this?

[petertodd]

Now that CLTV/CSV are available we can easily use them to provide this incentive.