Feathercoin - Analysis of possible maximum Transactions block / Dustcoin "attack" 25/10/2016

[wrapper]

@AmDD - Thanks for the info. @Aciddude has been exporting some of the records to csv, so he may get some more information on the block sizes. We also need to keep your dust spending mining results in mind for further info.

Any Overall details like the size of each transaction, which did or didn’t go though, how much each was for and the dust cost?

[wrapper]

@AmDD I’ve added a bit more analysis. This is a new chart zoomed into 3pm to 9pm 25/10/2016.

Feathercoin Number of Transactions - 3pm to 9pm 25/10/2016

This chart shows the high level of transactions.

Feathercoin Difficulty - - Zoomed into 3pm to 9pm 25/10/2016

This chart shows the variation difficulty zoomed into the dustcoin event. It shows the variation of Difficulty as the hash changes. Bottlenecks in making dust transactions will occur if the high hash is not accepting them and they are not required to take such a proportion, as is taken.
The zoom chart shows the timings in more detail, so you can see as the block times increase.

Feathercoin Block Times - Zoomed into 3pm to 9pm 25/10/2016

This chart shows Block times during the high level of transactions, zoomed in to 3pm to 9pm.

Feathercoin Transaction Values - Zoomed to 3-9pm 25/10/2016

This chart shows Transaction Values during the high level of transactions, zoomed in to 3pm to 9pm.

[wrapper]

Feathercoin High Value Block 9-11:30pm 25/10/2016

Feathercoin Difficulty zoomed in to 9-11:30pm 25/10/2016

The high value event crca 12:40pm does not seem to be co-incident with a high hash / difficulty event.
Perhaps a reason multipools should review their switching policy, the algoryths make the assumption the block fee is the only income.

[AcidD]

I did a “getpeerinfo” when had 83 peers connected to my Block Explorer

https://fsight.chain.tips/FTC_connected_nodes_23_05_2017.xlsx

On the above Excel sheet i’ve highlighted old clients and clients that shouldn’t be connecting to the FTC network.

[FlatBlack]

@aciddude soori to interupt…
.
by ‘clients that shouldn’t be connecting to the FTC network.’… can elaborate a bit more…?
.
again, so soori to interrupt…

[AcidD]

@FlatBlack said in Feathercoin - Analysis of possible maximum Transactions block / Dustcoin "attack" 25/10/2016:

@aciddude soori to interupt…
.
by ‘clients that shouldn’t be connecting to the FTC network.’… can elaborate a bit more…?
.
again, so soori to interrupt…

Have a look at the sheet and you tell me ;-)

[wrapper]

@FlatBlack You can use the Debug console in the help menu of the Feathercoin Wallet to send instructions and poll the network. One of those commands is “getpeerinfo” which tells the IP addresses connected to that node.

The original Bitcoin code from Satoshi, the peers.dat file was a text document, it has since been changed to a binary format. But, it is a peer to peer network and the code needs to connect to someone …

I suggest reading the Feathercoin guide :
https://github.com/wrapperband/FeathercoinWalletGuide

[wrapper]

@AmDD Further to consolidating dust payments, I was readings this :

https://bitcoin.stackexchange.com/questions/5583/how-can-i-combine-all-the-tiny-amounts-ive-received-to-minimise-transaction-fee

I’m sure similar criteria apply to FTC blockchain. e.g.

Quote :
"If your coins are old enough (say, 3 months for 10 BTC and a 200KB transaction size) [3], then the official client might not enforce the minimum fee on your transaction. Otherwise you may need to use a modified client that doesn’t enforce a minimum fee.

In any case you will need to point your client to Lightfoot Hosting’s free transaction relay, which will relay any transaction to the network [2], so it can be picked up by Eligius."

However, looks like over 1/3 of your dust payments got through. It would be interesting to see if that was due to the high proportion of Feathercoin p2pool, or other pool types not adjusting to prefer certain transactions.

[FlatBlack]

@aciddude :thumbsup_tone2: :sweat_smile:

[FlatBlack]

@wrapper thanx for d ‘simple-guide’ n link… :bow_tone1:

[AmDD]

@wrapper said in Feathercoin - Analysis of possible maximum Transactions block / Dustcoin "attack" 25/10/2016:

@AmDD Further to consolidating dust payments, I was readings this :

https://bitcoin.stackexchange.com/questions/5583/how-can-i-combine-all-the-tiny-amounts-ive-received-to-minimise-transaction-fee

I’m sure similar criteria apply to FTC blockchain. e.g.

Quote :
"If your coins are old enough (say, 3 months for 10 BTC and a 200KB transaction size) [3], then the official client might not enforce the minimum fee on your transaction. Otherwise you may need to use a modified client that doesn’t enforce a minimum fee.

In any case you will need to point your client to Lightfoot Hosting’s free transaction relay, which will relay any transaction to the network [2], so it can be picked up by Eligius."

However, looks like over 1/3 of your dust payments got through. It would be interesting to see if that was due to the high proportion of Feathercoin p2pool, or other pool types not adjusting to prefer certain transactions.

This was long enough ago that I dont remember the details and I didnt record the data anywhere. That being said, I remember doing 2-3 different runs, one of which was looped about 30,000 times. I recall seeing on the explorer that the transactions in the blocks did not add up to the 30-40,000 total transactions BUT my receiving wallet does have about 38,000 transactions into it so they all must have gone through. I’ll look into what my options are with the dust now - or Ill just hold it until FTC is $1000 each :)

[wrapper]

@AmDD cheers for the info.

@Flatblack

I assembled a guide for moderators doing support or FAQ, and not so frequently asked questions, you may find an informative read …

[Support] Mode of Failure Analysis. Part 1 - Faults, Causes and Solutions
http://forum.feathercoin.com/topic/4606/support-mode-of-failure-analysis-part-1-faults-causes-and-solutions

[Support] Mode of Failure Analysis. Part 2
http://forum.feathercoin.com/topic/4694/support-mode-of-failure-analysis-part-2-faults-causes-and-solutions

[Support] Mode of Failure Analysis. Part 3
http://forum.feathercoin.com/topic/4946/support-mode-of-failure-analysis-part-3-faults-causes-and-solutions

[FlatBlack]

@wrapper ayyyee, fren…
:bow_tone1: thanx a lot wit d links…
much appreciation…

[gonnaforget]

What’s up with all these attacks against FTC? Was it because there was someone who was big into a competing coin, or was it just for fun?

[wrapper]

@gonnaforget said in Feathercoin - Analysis of possible maximum Transactions block / Dustcoin "attack" 25/10/2016:

What’s up with all these attacks against FTC? Was it because there was someone who was big into a competing coin, or was it just for fun?

There are a few things quoted as “Attacks”. There have not been times when it is proved there is a deliberate attack, i.e. someone has paid or has enough power to try to double spend.

This resulted in the first major update to Feathercoin to implement Automatic Check pointing or ACP. Once this happened and there was a “double spend issue”, FTC would reject that chain - i.e. It becomes an Orphan chain.

However, Feathercoin still abides by the normal rules and the longest chain wins. So there are 2 competing chains untill the attacker error chain gives up or the normal chain becomes longer.

There similar reasons Bitcoin has also suffered longer orphan chains than originally specified, but FTC does suffer a couple of long chains early on.

There is another known “attack”, it turned out to be someone testing, one was an attempt to flood the network with dust payments, was noticed later but had no detrimental effect.

I designed eHRC initially as a potential replacement for ACP but in the end it was used to reduce the effect of coin switching. It does make it harder for someone to achieve network dominance for long enough to do anything. So we don’t tend to get the long orphan chains.