https://bitescrow.dev/resources/intro
"
Some challenges with the current model:
The escrow agent has the ability to censor members of a contract by ignoring their statements. While the use of receipts forces the agent to censor in real-time, this is still an issue.
In the future, we will be leveraging the Nostr network in order to provide a proof-of-delivery system that will force to escrow agent to censor everyone, or no-one.
Even with the covenant restrictions and fraud-proofs, the escrow agent may still act malicious and settle the contract unfairly. This is a risk inhereit with any escrow system.
While the protocol attempts to both disincentivize and marginalize this risk as much as possible, it is still an issue in certain cases (for example, if the escrow agent is hacked or coerced).
In the future, we plan to mitigate these risks even further, using two mechanisms:
Splitting the escrow agent role into a federation, using threshold signatures (FROST).
Using a proof-of-stake system to punish agents if proof of fraud is presented."
will be interesting to see this evolving
zoomoutpls
npub1ps5…ylka
2024-06-03 07:51:54
Author Public Key
npub1ps5mp2hrs4w8973cxkn8nfvxquqrn6ems4ntkgtwthwmzefezapqkuylkaPublished at
2024-06-03 07:51:54Event JSON
{
"id": "07a37378a1ba206439f84b8e3ccbff3cee8b3467f7daf0de72fb92d7163feda5",
"pubkey": "0c29b0aae3855c72fa3835a679a586070039eb3b8566bb216e5dddb165391742",
"created_at": 1717393914,
"kind": 1,
"tags": [
[
"r",
"https://bitescrow.dev/resources/intro"
]
],
"content": "https://bitescrow.dev/resources/intro\n\n\"\nSome challenges with the current model:\n\n The escrow agent has the ability to censor members of a contract by ignoring their statements. While the use of receipts forces the agent to censor in real-time, this is still an issue.\n\n In the future, we will be leveraging the Nostr network in order to provide a proof-of-delivery system that will force to escrow agent to censor everyone, or no-one.\n\n Even with the covenant restrictions and fraud-proofs, the escrow agent may still act malicious and settle the contract unfairly. This is a risk inhereit with any escrow system.\n\n While the protocol attempts to both disincentivize and marginalize this risk as much as possible, it is still an issue in certain cases (for example, if the escrow agent is hacked or coerced).\n\n In the future, we plan to mitigate these risks even further, using two mechanisms:\n Splitting the escrow agent role into a federation, using threshold signatures (FROST).\n Using a proof-of-stake system to punish agents if proof of fraud is presented.\"\n\n\nwill be interesting to see this evolving",
"sig": "2e75685d22061a1f905d51794ecb3a27f8a51eec6eb136f1df7c87b2eb2bca1b60f602e56f4ca68d6b3b006da58e52b8d8f75ac6486d421a32a513cf2b5f93ad"
}