[ANN][XEL] Elastic Project - The Decentralized Supercomputer

[trader19]

I'm not forging anymore, @trader19 could you please send about 20 various transactions to me and anyone else and confirm that everything is ok? And please don't send more than 2 transactions per block. Thanks.

sent you 20 various transactions on block 4112,4113,4114,4115,4116 pls check.

[1714214252]

1714214252

[1714214252]

1714214252

[1714214252]

1714214252

[1714214252]

1714214252

[1714214252]

1714214252

[ImI]

I'm not forging anymore, @trader19 could you please send about 20 various transactions to me and anyone else and confirm that everything is ok? And please don't send more than 2 transactions per block. Thanks.

sent you 20 various transactions on block 4112,4113,4114,4115,4116 pls check.

i see several TXs at block# 4116-4119

edit: only peer at the moment 108.61.xxx

edit2: apart from me no one else seems to forge

[trader19]

I'm not forging anymore, @trader19 could you please send about 20 various transactions to me and anyone else and confirm that everything is ok? And please don't send more than 2 transactions per block. Thanks.

sent you 20 various transactions on block 4112,4113,4114,4115,4116 pls check.

i see several TXs at block# 4116-4119

edit: only peer at the moment 108.61.xxx

edit2: apart from me no one else seems to forge

yes that's my node server, we might have several forks running because like you seems that i am the only one forging  lol 

[BigBoom3599]

I'm still forging aswell but the XELs that ImI sent me haven't matured yet so I won't find a block very often, 108.61.177.169 is my only node too.

[Ghoom]

XEL-4VAN-Z84K-38SX-GGNPQ

thanks

[Evil-Knievel]

You guys are awesome! Sorry for the long response times, but as I told before I am in my vacation and only online when I find an open wifi on the go.
Things will improve once I get back in 2 days. Then, I will be working full time again.

Regarding the testnet, seems like someone again identified an edge case where transactions end up in the mempool being broadcast even though they are invalid. This causes the two public nodes hosted on AWS to be blacklisted:

Code:

nxt.NxtException$NotValidException: Cannot cancel already cancelled or finished work
	at nxt.TransactionType$WorkControl$3.validateAttachment(TransactionType.java:532)
	at nxt.Attachment$AbstractAttachment.validate(Attachment.java:34)
	at nxt.TransactionImpl.validate(TransactionImpl.java:835)
	at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:478)
	at nxt.TransactionProcessorImpl.access$8(TransactionProcessorImpl.java:448)
	at nxt.TransactionProcessorImpl$5.run(TransactionProcessorImpl.java:217)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
2016-09-04 18:37:00 FINE: TransactionProcessorImpl.processPeerTransactions: Invalid transaction from peer: {"senderPublicKey":"ae0df06215caa34bf680a84b24330554d0af092b925b5bcf8704ac31cd489019","attachment":{"id":"1309865111079249537","version.WorkIdentifierCancellationRequest":1},"subtype":5,"amountNQT":0,"signature":"f7e891e4e4965e765a1b11e31ac289770b2f5f3994346c8bc0701a500aee180de53e87bdb782e0846c0477c86b6341b6d8627b079c1946efdcb3e387fffacca1","feeNQT":0,"ecBlockHeight":3941,"type":3,"deadline":1440,"version":1,"timestamp":21374693,"ecBlockId":"11763907846096637330"}
nxt.NxtException$NotValidException: Cannot cancel already cancelled or finished work
	at nxt.TransactionType$WorkControl$3.validateAttachment(TransactionType.java:532)
	at nxt.Attachment$AbstractAttachment.validate(Attachment.java:34)
	at nxt.TransactionImpl.validate(TransactionImpl.java:835)
	at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:478)
	at nxt.TransactionProcessorImpl.access$8(TransactionProcessorImpl.java:448)
	at nxt.TransactionProcessorImpl$5.run(TransactionProcessorImpl.java:217)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
2016-09-04 18:37:00 FINE: PeerImpl.blacklist: Blacklisting 52.57.31.137 because of: nxt.NxtException$NotValidException: Peer sends invalid transactions

If you set your "blacklisting time" to 1s or 0s or so, in net-default.conf, then you will be able to stay connected with these nodes.

I repeat, if someone can identify and fix this mistake before I do, I will give him 2 BTC of my personal savings. Thanks for stress testing! The testnet was the first test of Elastic and it was expected to have bugs. The more we identify the more stable we will eventually become! Thanks for everyone.


My feeling tells me, that we need a sophisticated mempool cleanup routine, which cleans up all bounties/work closures/POW submissions that are still pending when a work is being closed, and not broadcast regardless of the work's state!


... I will do some code reading today as well, and check out what kind of transactions are being broadcast by the AWS nodes and why!

[Evil-Knievel]

Close elastic, wait 10 minutes for blacklist to expire, git pull; ./compile.sh; ./run.sh
... no need to reload the blockchain! What do you think?

The first suggestion for a possible fix for that problem is here:
https://github.com/OrdinaryDude/elastic-reference-client/commit/1ae69559c2faa97c641293d65f8decf3f6470d25

[trader19]

Close elastic, wait 10 minutes for blacklist to expire, git pull; ./compile.sh; ./run.sh
... no need to reload the blockchain! What do you think?

The first suggestion for a possible fix for that problem is here:
https://github.com/OrdinaryDude/elastic-reference-client/commit/1ae69559c2faa97c641293d65f8decf3f6470d25

updated, you are quick  when you have some time can you please take a look at problem i have since the start? i cant register account name and can't submit new work because i am getting this error:

Code:

Could not verify signature (server side).

thx

[hagie]

Hi,

I've set up a public available testserver:

The Server can be reached by http(s)://elastic.cryptnodes.site

If someone could send my some Testnet - XEL I will be happy: XEL-48LM-K27E-ZXWE-FFFF2

IMHO it would be beneficial if we could restrict the host from which minting/forging could be enabled or disable the option completely.  This made it easier to run a public wallet.

Regards

[hagie]

The node also runs as fullnode - p2p is accesable from outside - maybe this could help in some way.

I saw "German" is still beta - If you send ma a language resource file I could look into it and help translating (native german)

regards

[BigBoom3599]

I've noticed that the stats listed on the blocks and peers page (e.g. # Forged Blocks, Uploade Volume, Downloaded Volume) change often (mostly decrease), I think it changes depending on which nodes you're connected to, Is this just the way its stored or is this something else?

[unvoid]

Do you work on work/bounties when forging or do you need a seperate miner for that?

You need separate miner for that. But miner isn't working with testnet. I sent to @EK pull request to fix miner but @EK so far didn't merged it.

[unvoid]

Updated my node with your changes @EK. Submitted 5 another works and soon after my node is banned again and I'm on a fork.

@EK I'll not submit any work to the network untill you will be back from your vacation. I need to have quite working node to focus on blockchain explorer. Also please merge my pull request for miner so more people could do PoW in testnet. Thanks!

[unvoid]

Hi,

I've set up a public available testserver:

The Server can be reached by http(s)://elastic.cryptnodes.site

If someone could send my some Testnet - XEL I will be happy: XEL-48LM-K27E-ZXWE-FFFF2

IMHO it would be beneficial if we could restrict the host from which minting/forging could be enabled or disable the option completely.  This made it easier to run a public wallet.

Regards

Great! More nodes more fun for us all. Please write pm to @ImI for some test XEL. He should send you more than regular since you're running 24/7 node. I'll send you some coins also as soon as my node will be operational.

[xibeijan]

Someone please send me some test XEL

XEL-23G9-RYXH-G7EU-3UUHX
e7aa3878eea460bbe4041e1bc8983bf3fae56445fec61f169f8d5b18beb5ee54

I want to help out.

[hagie]

Hi,

I've set up a public available testserver:

The Server can be reached by http(s)://elastic.cryptnodes.site

If someone could send my some Testnet - XEL I will be happy: XEL-48LM-K27E-ZXWE-FFFF2

IMHO it would be beneficial if we could restrict the host from which minting/forging could be enabled or disable the option completely.  This made it easier to run a public wallet.

Regards

Great! More nodes more fun for us all. Please write pm to @ImI for some test XEL. He should send you more than regular since you're running 24/7 node. I'll send you some coins also as soon as my node will be operational.

@ImI ?? Who is ImI ? A user here at the BTCT ?

yes I 'll run it 24/7 and try to stay as up to date as possible.

regards

[unvoid]

Just sent transaction from my node. Network discarded it. Again it's my PoW submissions I think.

@EK My nxt.log:

http://s000.tinyupload.com/index.php?file_id=04482194844896188085

[unvoid]

Hi,

I've set up a public available testserver:

The Server can be reached by http(s)://elastic.cryptnodes.site

If someone could send my some Testnet - XEL I will be happy: XEL-48LM-K27E-ZXWE-FFFF2

IMHO it would be beneficial if we could restrict the host from which minting/forging could be enabled or disable the option completely.  This made it easier to run a public wallet.

Regards

Great! More nodes more fun for us all. Please write pm to @ImI for some test XEL. He should send you more than regular since you're running 24/7 node. I'll send you some coins also as soon as my node will be operational.

@ImI ?? Who is ImI ? A user here at the BTCT ?

yes I 'll run it 24/7 and try to stay as up to date as possible.

regards

Yes. Just read 2-3 pages back and you will find him.

[xibeijan]

Just saw 170,000 appear then disappear.   Is that enough to forge with?  Would be good to test forging with lots of participants.

[trader19]

Just sent transaction from my node. Network discarded it. Again it's my PoW submissions I think.

@EK My nxt.log:

http://s000.tinyupload.com/index.php?file_id=04482194844896188085

yes must have something to do with your submitted work, i am getting bunch off errors:

Code:

Discarded Bounty Submission for work_id=8439169722941893793, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=8439169722941893793, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=8439169722941893793, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=8439169722941893793, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=8439169722941893793, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=8439169722941893793, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=8439169722941893793, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=8439169722941893793, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=8439169722941893793, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=8439169722941893793, number exceeded! confirmed left = 10, unconfirmed pending = 10

its almost like you are DDOSing the network..

Just saw 170,000 appear then disappear.   Is that enough to forge with?  Would be good to test forging with lots of participants.

yea, that was me sending to you but looks like network forked again.. we should wait for EK