📅 Original date posted:2015-01-23
📝 Original message:Correct, plus the most likely scenario in such attack is that the malware
even don't push such tx with excessive fees to the network, but send it
directly to attacker's pool/miner.
M.
On Fri, Jan 23, 2015 at 4:42 PM, Alan Reiner <etotheipi at gmail.com> wrote:
> Unfortunately, one major attack vector is someone isolating your node,
> getting you to sign away your whole wallet to fee, and then selling it to a
> mining pool to mine it before you can figure why your transactions aren't
> making it to the network. In such an attack, the relay rules aren't
> relevant, and if the attacker can DoS you for 24 hours, it doesn't take a
> ton of mining power to make the attack extremely likely to succeed.
>
>
>
>
> On 01/23/2015 10:31 AM, Tamas Blummer wrote:
>
> Not a fix, but would reduce the financial risk, if nodes were not relaying
> excessive fee transactions.
>
> Tamas Blummer
>
>
>
>
>
> ------------------------------------------------------------------------------
> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
> GigeNET is offering a free month of service with a new server in Ashburn.
> Choose from 2 high performing configs, both with 100TB of bandwidth.
> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
> http://p.sf.net/sfu/gigenet
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150123/2562323d/attachment.html>;
slush [ARCHIVE] /
npub1ad…gl2p6
2023-06-07 15:29:06
in reply to nevent1q…rnlf
Author Public Key
npub1ad7209g90jnu400x74quws0xv8gpxs2fxnjexnpwqnrxwa39exdq5gl2p6Published at
2023-06-07 15:29:06Event JSON
{
"id": "20bbd9e9f7af6719b2a73b0e6bb222766b7b295b8259a5cfca389143ff57e4d7",
"pubkey": "eb7ca795057ca7cabde6f541c741e661d013414934e5934c2e04c6677625c99a",
"created_at": 1686151746,
"kind": 1,
"tags": [
[
"e",
"6dc832bdb706e2f61589ea679669c46a49f00ca991f53b93fef09a1a229115c6",
"",
"root"
],
[
"e",
"466fcecd52cf5107277a85cdcd96bae71f5e6546e95d2e6848baaba9a37bbb19",
"",
"reply"
],
[
"p",
"86f42bcb76a431c128b596c36714ae73a42cae48706a9e5513d716043447f5ec"
]
],
"content": "📅 Original date posted:2015-01-23\n📝 Original message:Correct, plus the most likely scenario in such attack is that the malware\neven don't push such tx with excessive fees to the network, but send it\ndirectly to attacker's pool/miner.\n\nM.\n\nOn Fri, Jan 23, 2015 at 4:42 PM, Alan Reiner \u003cetotheipi at gmail.com\u003e wrote:\n\n\u003e Unfortunately, one major attack vector is someone isolating your node,\n\u003e getting you to sign away your whole wallet to fee, and then selling it to a\n\u003e mining pool to mine it before you can figure why your transactions aren't\n\u003e making it to the network. In such an attack, the relay rules aren't\n\u003e relevant, and if the attacker can DoS you for 24 hours, it doesn't take a\n\u003e ton of mining power to make the attack extremely likely to succeed.\n\u003e\n\u003e\n\u003e\n\u003e\n\u003e On 01/23/2015 10:31 AM, Tamas Blummer wrote:\n\u003e\n\u003e Not a fix, but would reduce the financial risk, if nodes were not relaying\n\u003e excessive fee transactions.\n\u003e\n\u003e Tamas Blummer\n\u003e\n\u003e\n\u003e\n\u003e\n\u003e\n\u003e ------------------------------------------------------------------------------\n\u003e New Year. New Location. New Benefits. New Data Center in Ashburn, VA.\n\u003e GigeNET is offering a free month of service with a new server in Ashburn.\n\u003e Choose from 2 high performing configs, both with 100TB of bandwidth.\n\u003e Higher redundancy.Lower latency.Increased capacity.Completely compliant.\n\u003e http://p.sf.net/sfu/gigenet\n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150123/2562323d/attachment.html\u003e",
"sig": "6f2d955f1849f075cf8d57036c3ae7673fad32eee3bec432963270ff366567ac11af77daf5165dcfac10666a25f011e0af8da0f5c2c11f85be908feeacf7ea35"
}