📅 Original date posted:2019-08-06
📝 Original message:В Mon, 5 Aug 2019 20:04:26 +0100
Chris Belcher <belcher at riseup.net> wrote:
> So what's needed is a way to make renting out TXOs impossible or very
> difficult.
You can make renting the TXOs risky for the attacker. Make it so that
the entity that rented out the TXO can revoke the participation of said
TXO in the market, by publishing some special signature. That act of
revocation can also mean revocation of all other TXOs that were used in
a bond alongside it. This way, any entity that wants to spoil an
attacker's consolidation via rent, can rent out its TXO to the
attacker, and then revoke it, spoiling the whole package the attacker
have consolidated.
There may be other way to impose penalties.
For example, all locked TXO may be required to be spendable by *any*
key that controls any TXO in the 'bond TXO package'. I think this
should be possible with taproot - you will have to publish a taproot
trees for your locked TXOs (say, N of them), and the tree for each TXO
will have N leaves, each leaf will specify a condition "spendable by
the key N". This way, if I give you my TXO to include it in a bond by
locking it, you also need to make your other TXOs in a bond spendable
by me.
For both scenarios to work for the attacker, there's need to be an
off-chain contractual relationship between the parties. Otherwise the
entity that rents out the TXOs can spoil or just confiscate the bond of
the entity that rented them, without reprecussions.
Dmitry Petukhov [ARCHIVE] /
npub10r…9afdw
2023-06-07 18:19:56
in reply to nevent1q…xp9x
Author Public Key
npub10r66s2stvnancx9axwnfc5a34asjkwkgmkq7ztm5hf30x7fa4szsv9afdwPublished at
2023-06-07 18:19:56Event JSON
{
"id": "4c542afffe283023d7d0ca2fbc66e99ab70a0804ea3fc8a0cc38807dfcaed3ab",
"pubkey": "78f5a82a0b64fb3c18bd33a69c53b1af612b3ac8dd81e12f74ba62f3793dac05",
"created_at": 1686161996,
"kind": 1,
"tags": [
[
"e",
"a08dce3b67359ed00d4e2ce273a5fce8912dd2b587c89f8e261331c71b6b29ce",
"",
"root"
],
[
"e",
"588555f6d2505aa2df639a518ebcdce0e95e836825c17b2e67615fcfcf9787ff",
"",
"reply"
],
[
"p",
"4505072744a9d3e490af9262bfe38e6ee5338a77177b565b6b37730b63a7b861"
]
],
"content": "📅 Original date posted:2019-08-06\n📝 Original message:В Mon, 5 Aug 2019 20:04:26 +0100\nChris Belcher \u003cbelcher at riseup.net\u003e wrote:\n\n\u003e So what's needed is a way to make renting out TXOs impossible or very\n\u003e difficult.\n\nYou can make renting the TXOs risky for the attacker. Make it so that\nthe entity that rented out the TXO can revoke the participation of said\nTXO in the market, by publishing some special signature. That act of\nrevocation can also mean revocation of all other TXOs that were used in\na bond alongside it. This way, any entity that wants to spoil an\nattacker's consolidation via rent, can rent out its TXO to the\nattacker, and then revoke it, spoiling the whole package the attacker\nhave consolidated.\n\nThere may be other way to impose penalties.\n\nFor example, all locked TXO may be required to be spendable by *any*\nkey that controls any TXO in the 'bond TXO package'. I think this\nshould be possible with taproot - you will have to publish a taproot\ntrees for your locked TXOs (say, N of them), and the tree for each TXO\nwill have N leaves, each leaf will specify a condition \"spendable by\nthe key N\". This way, if I give you my TXO to include it in a bond by\nlocking it, you also need to make your other TXOs in a bond spendable\nby me.\n\nFor both scenarios to work for the attacker, there's need to be an\noff-chain contractual relationship between the parties. Otherwise the\nentity that rents out the TXOs can spoil or just confiscate the bond of\nthe entity that rented them, without reprecussions.",
"sig": "d9b3d57343bb5f8242d73627fda50376a9539a72f5262418661b8a548a42aaa0c9748c58c656d4e579b70acd6e0ed4e0f56f52c6d86946773e1f14571cc0f3c2"
}