📅 Original date posted:2021-10-07
📝 Original message:If u allow me to discuss,,,
I previously suggested storing dust UTXOS in a separate Merkle tree or
strucutre in general if we are talking about the original set.
I'm a kind of person who doesn't like to throw any thing; if it's not
needed now keep it in the basement for example.
So, if dust UTXOS making a burden keep them in secondary storage, where in
such cases u can verify then delete them.
On Thu, Oct 7, 2021, 06:52 ZmnSCPxj via bitcoin-dev <
bitcoin-dev at lists.linuxfoundation.org> wrote:
> Good morning e,
>
> > mostly thinking out loud
> >
> > suppose there is a "lightweight" node:
> >
> > 1. ignores utxo's below the dust limit
> > 2. doesn't validate dust tx
> > 3. still validates POW, other tx, etc.
> >
> > these nodes could possibly get forked - accepting a series of valid,
> > mined blocks where there is an invalid but ignored dust tx, however
> > this attack seems every bit as expensive as a 51% attack
>
> How would such a node treat a transaction that spends multiple dust UTXOs
> and creates a single non-dust UTXO out of them (after fees)?
> Is it valid (to such a node) or not?
>
> I presume from #1 it never stores dust UTXOs, so the node cannot know if
> the UTXO being spent by such a tx is spending dust, or trying to spend an
> already-spent TXO, or even inventing a TXO out of `/dev/random`.
>
> Regards,
> ZmnSCPxj
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20211007/3889c77d/attachment.html>;
shymaa arafat [ARCHIVE] /
npub1l7…hgr56
2023-06-07 22:59:48
in reply to nevent1q…5svm
Author Public Key
npub1l7ldumxqplqv4h9lfkwpwp3lapj3xnla2hnf8h8mm9da3qlv6shqfhgr56Published at
2023-06-07 22:59:48Event JSON
{
"id": "7f328cd074972376489bf89bc701ec3d0816b593cd76b083fabeb0f7b18b8793",
"pubkey": "ffbede6cc00fc0cadcbf4d9c17063fe865134ffd55e693dcfbd95bd883ecd42e",
"created_at": 1686178788,
"kind": 1,
"tags": [
[
"e",
"253f5d7bc6975c77193fd9562401b6feaa0355ffaa6137785c44a341508d5545",
"",
"root"
],
[
"e",
"38158db097a56fd5f70d8e51af8012d7c2612bf5046731f2320ad14bc033f4e9",
"",
"reply"
],
[
"p",
"22944ce1e29904e3826d25013a614e4665693ec514003efacc1b7586e8e5d0aa"
]
],
"content": "📅 Original date posted:2021-10-07\n📝 Original message:If u allow me to discuss,,,\nI previously suggested storing dust UTXOS in a separate Merkle tree or\nstrucutre in general if we are talking about the original set.\nI'm a kind of person who doesn't like to throw any thing; if it's not\nneeded now keep it in the basement for example.\nSo, if dust UTXOS making a burden keep them in secondary storage, where in\nsuch cases u can verify then delete them.\n\n\n\nOn Thu, Oct 7, 2021, 06:52 ZmnSCPxj via bitcoin-dev \u003c\nbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\n\u003e Good morning e,\n\u003e\n\u003e \u003e mostly thinking out loud\n\u003e \u003e\n\u003e \u003e suppose there is a \"lightweight\" node:\n\u003e \u003e\n\u003e \u003e 1. ignores utxo's below the dust limit\n\u003e \u003e 2. doesn't validate dust tx\n\u003e \u003e 3. still validates POW, other tx, etc.\n\u003e \u003e\n\u003e \u003e these nodes could possibly get forked - accepting a series of valid,\n\u003e \u003e mined blocks where there is an invalid but ignored dust tx, however\n\u003e \u003e this attack seems every bit as expensive as a 51% attack\n\u003e\n\u003e How would such a node treat a transaction that spends multiple dust UTXOs\n\u003e and creates a single non-dust UTXO out of them (after fees)?\n\u003e Is it valid (to such a node) or not?\n\u003e\n\u003e I presume from #1 it never stores dust UTXOs, so the node cannot know if\n\u003e the UTXO being spent by such a tx is spending dust, or trying to spend an\n\u003e already-spent TXO, or even inventing a TXO out of `/dev/random`.\n\u003e\n\u003e Regards,\n\u003e ZmnSCPxj\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20211007/3889c77d/attachment.html\u003e",
"sig": "9f037df1c2331ebdd1a27c951efa38b26d4e23c625c22e5c8fb06286462e1474856a563a0e2e1c6c272f459af6d3ecba0ab61e0ec44a085e63b82acad9c17339"
}