Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
lclc opened this issue Feb 3, 2015 · 8 comments
Open

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

lclc opened this issue Feb 3, 2015 · 8 comments

Comments

@lclc
Copy link

lclc commented Feb 3, 2015

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
Copy link
Contributor

809894ac commented Feb 5, 2015

https://www.mail-archive.com/bitcoin-development@lists.sourceforge.net/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
Copy link

leijurv commented Feb 5, 2015

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

@809894ac
Copy link
Contributor

809894ac commented Feb 7, 2015

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
Copy link

@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
Copy link

btcdrak commented Feb 11, 2015

Just run DarkLeaks on Viacoin blockchain which already implements CHECKLOCKTIMEVERIFY.

@0kino7ori
Copy link

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
Copy link

HostFat commented Jul 4, 2016

Any news on this?

@petertodd
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants