Bitcoin Forum
August 20, 2018, 04:15:08 AM *
News: Latest stable version of Bitcoin Core: 0.16.2  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 [77] 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 ... 347 »
  Print  
Author Topic: [ANN][XEL] Elastic Project - The Decentralized Supercomputer  (Read 448526 times)
This is a self-moderated topic. If you do not want to be moderated by the person who started this topic, create a new topic.
unvoid
Hero Member
*****
Offline Offline

Activity: 535
Merit: 500



View Profile
September 02, 2016, 07:18:30 PM
 #1521

Code:
Discarded Bounty Submission for work_id=-7105383925191439880, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=-7105383925191439880, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=-7105383925191439880, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=4210165941331695358, number exceeded! confirmed left = 2, unconfirmed pending = 2
Discarded Bounty Submission for work_id=-7105383925191439880, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=-7105383925191439880, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=-7105383925191439880, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=-7105383925191439880, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=-7105383925191439880, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=-7105383925191439880, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=-7105383925191439880, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=-7105383925191439880, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=-7105383925191439880, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=-7105383925191439880, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=4210165941331695358, number exceeded! confirmed left = 2, unconfirmed pending = 2
Discarded Bounty Submission for work_id=4210165941331695358, number exceeded! confirmed left = 2, unconfirmed pending = 2
Discarded Bounty Submission for work_id=-7105383925191439880, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=-7105383925191439880, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=-7105383925191439880, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=-7105383925191439880, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=4210165941331695358, number exceeded! confirmed left = 2, unconfirmed pending = 2
Discarded Bounty Submission for work_id=-7105383925191439880, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=-7105383925191439880, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=-7105383925191439880, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=-7105383925191439880, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=-7105383925191439880, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=-7105383925191439880, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=4210165941331695358, number exceeded! confirmed left = 2, unconfirmed pending = 2
Discarded Bounty Submission for work_id=-7105383925191439880, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=-7105383925191439880, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=-7105383925191439880, number exceeded! confirmed left = 10, unconfirmed pending = 10
Clearing inactive listener: 69658237
Discarded Bounty Submission for work_id=-7105383925191439880, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=4210165941331695358, number exceeded! confirmed left = 2, unconfirmed pending = 2
Discarded Bounty Submission for work_id=-7105383925191439880, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=-7105383925191439880, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=-7105383925191439880, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=-7105383925191439880, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=-7105383925191439880, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=-7105383925191439880, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=4210165941331695358, number exceeded! confirmed left = 2, unconfirmed pending = 2
Discarded Bounty Submission for work_id=-7105383925191439880, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=-7105383925191439880, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=-7105383925191439880, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=-7105383925191439880, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=-7105383925191439880, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=-7105383925191439880, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=-7105383925191439880, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=-7105383925191439880, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=-7105383925191439880, number exceeded! confirmed left = 10, unconfirmed pending = 10
Discarded Bounty Submission for work_id=-7105383925191439880, number exceeded! confirmed left = 10, unconfirmed pending = 10


I clearly flooded my node (network?) with bounty submissions. I have ton of those messages. DoS from my side?

@EK we have serious problem here. I can't even cancel my work. This work is hung at oblivion. And 4 more works waiting for start so we are deep in satan ass without you.

BTC: 1CMgHWx4wkAaAy2FfeCyPdedUExmhGhfi5
XEL: XEL-HCM8-KB6E-YFLK-8BWMF
1534738508
Hero Member
*
Offline Offline

Posts: 1534738508

View Profile Personal Message (Offline)

Ignore
1534738508
Reply with quote  #2

1534738508
Report to moderator
BOUNTY PORTALS
BLOG
WHERE BOUNTY MANAGEMENT
MEETS AUTOMATION
SIGNATURE CAMPAIGNS
TWITTER
FACEBOOK
MEDIA CAMPAIGNS
AND MORE!
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1534738508
Hero Member
*
Offline Offline

Posts: 1534738508

View Profile Personal Message (Offline)

Ignore
1534738508
Reply with quote  #2

1534738508
Report to moderator
1534738508
Hero Member
*
Offline Offline

Posts: 1534738508

View Profile Personal Message (Offline)

Ignore
1534738508
Reply with quote  #2

1534738508
Report to moderator
1534738508
Hero Member
*
Offline Offline

Posts: 1534738508

View Profile Personal Message (Offline)

Ignore
1534738508
Reply with quote  #2

1534738508
Report to moderator
trader19
Legendary
*
Offline Offline

Activity: 1232
Merit: 1001



View Profile WWW
September 02, 2016, 08:22:20 PM
 #1522

@EK we have big problem here. I submitted 6 works to the network (at once) and first work can't get to end. Bounty found is 0 for an hour and nothing is changing. Another 5 jobs waiting for execute but first one is stuck.
same with transaction, i sent 100k to BigBoom3599 and it keeps appearing and disappearing from transaction history. its like transaction is not getting picked by node, same with messaging. sent an answer to unvoid 1h ago its still not delivered.

@trader19 if you'll have 24/7 node please paste here your IP address so we can add it to the testnetPeers in next release.
@unvoid do we have any instruction to install full node with web interface under ubuntu 14.4? i am stuck with bunch of java errors
EDIT: watching video just now lol
EDIT2: i am clearly missing some deps. ?
Do you have any error? Java >=1.8 is base dep. You can check your Java version by running:
Code:
java -version
in terminal
i got it working on ubuntu vultr server, i can see my peer appeared in the peer list and i have interface access on my node.
i will keep node running for few days.
thanks

Join the Elastic revolution!  Elastic - The Decentralized Supercomputer
ELASTIC WEBSITE | NEW ANNOUNCEMENT THREAD | ELASTIC SLACK | ELASTIC FORUM
Evil-Knievel
Legendary
*
Offline Offline

Activity: 1204
Merit: 1149



View Profile
September 02, 2016, 09:46:38 PM
 #1523

Wow, unvoid! It looks like you have found just another glitch! I think Lannister would send you 2 more BTC (as I recall you are eligible for the first bug bounty as well) if you can reproduce what happened.

This is the error log:

Code:
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-02 23:43:20 FINE: TransactionProcessorImpl.processPeerTransactions: Invalid transaction from peer: {"senderPublicKey":"ae0df06215caa34bf680a84b24330554d0af092b925b5bcf8704ac31cd489019","signature":"d9a188015ff1c333095bb417833ee2baef34baa6eb23db4d5b7bd791c4d88b01de4059f9682553ac6ff1d96f86b352939befbdc6df22c3d513045fa3ac88a612","feeNQT":0,"type":3,"version":1,"ecBlockId":"2573426999249322481","attachment":{"input":[227557251,-1921958936,-762815411],"version.PiggybackedProofOfWork":1,"id":"4210165941331695358"},"subtype":2,"amountNQT":1000000000,"recipient":"12808828738982832951","ecBlockHeight":2242,"deadline":1440,"timestamp":21236953}
nxt.NxtException$NotValidException: Cannot submit POW for an already cancelled or finished work
at nxt.TransactionType$WorkControl$4.validateAttachment(TransactionType.java:641)
at nxt.Attachment$AbstractAttachment.validate(Attachment.java:34)
at nxt.TransactionImpl.validate(TransactionImpl.java:835)
at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:468)
at nxt.TransactionProcessorImpl.access$8(TransactionProcessorImpl.java:440)
at nxt.TransactionProcessorImpl$5.run(TransactionProcessorImpl.java:211)
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-02 23:43:20 FINE: TransactionProcessorImpl.processPeerTransactions: Invalid transaction from peer: {"senderPublicKey":"ae0df06215caa34bf680a84b24330554d0af092b925b5bcf8704ac31cd489019","signature":"7bad419fa86d3389dcecb9c87f7bf4a1aac1996bd570f1f56721e7d536cc250bf18c7cb7687db1c256048176e5509f0150ff0df0c2a9cb0864db82d79a3ce680","feeNQT":0,"type":3,"version":1,"ecBlockId":"9110437482347234720","attachment":{"input":[1908206150,-339794908,-1895261197],"version.PiggybackedProofOfWork":1,"id":"4210165941331695358"},"subtype":2,"amountNQT":1000000000,"recipient":"12808828738982832951","ecBlockHeight":2243,"deadline":1440,"timestamp":21237068}
nxt.NxtException$NotValidException: Cannot submit POW for an already cancelled or finished work
at nxt.TransactionType$WorkControl$4.validateAttachment(TransactionType.java:641)
at nxt.Attachment$AbstractAttachment.validate(Attachment.java:34)
at nxt.TransactionImpl.validate(TransactionImpl.java:835)
at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:468)
at nxt.TransactionProcessorImpl.access$8(TransactionProcessorImpl.java:440)
at nxt.TransactionProcessorImpl$5.run(TransactionProcessorImpl.java:211)
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-02 23:43:20 FINE: TransactionProcessorImpl.processPeerTransactions: Invalid transaction from peer: {"senderPublicKey":"ae0df06215caa34bf680a84b24330554d0af092b925b5bcf8704ac31cd489019","signature":"377a1355b86c0465139542b7994c5c5a999eac25774f1e54076242a6d4232707c8d534fe54ee7fb53cfddd67176cf79f1a8591b4c49e1755301fee0eb21a14ae","feeNQT":0,"type":3,"version":1,"ecBlockId":"12998068690024528804","attachment":{"input":[518577662,1779649994,1251435883],"version.PiggybackedProofOfWork":1,"id":"4210165941331695358"},"subtype":2,"amountNQT":1000000000,"recipient":"12808828738982832951","ecBlockHeight":2244,"deadline":1440,"timestamp":21237090}
nxt.NxtException$NotValidException: Cannot submit POW for an already cancelled or finished work
at nxt.TransactionType$WorkControl$4.validateAttachment(TransactionType.java:641)
at nxt.Attachment$AbstractAttachment.validate(Attachment.java:34)
at nxt.TransactionImpl.validate(TransactionImpl.java:835)
at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:468)
at nxt.TransactionProcessorImpl.access$8(TransactionProcessorImpl.java:440)
at nxt.TransactionProcessorImpl$5.run(TransactionProcessorImpl.java:211)
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)
java.lang.RuntimeException: Proof of work is invalid: does not meet target
at nxt.WorkLogicManager.validatePOW(WorkLogicManager.java:1199)
at nxt.TransactionType$WorkControl$4.validateAttachment(TransactionType.java:661)
at nxt.Attachment$AbstractAttachment.validate(Attachment.java:34)
at nxt.TransactionImpl.validate(TransactionImpl.java:835)
at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:468)
at nxt.TransactionProcessorImpl.access$8(TransactionProcessorImpl.java:440)
at nxt.TransactionProcessorImpl$5.run(TransactionProcessorImpl.java:211)
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-02 23:43:20 FINE: TransactionProcessorImpl.processPeerTransactions: Invalid transaction from peer: {"senderPublicKey":"ae0df06215caa34bf680a84b24330554d0af092b925b5bcf8704ac31cd489019","signature":"0abe685bdb4060c9d1ed9fe4f471b973797256ce07e37ff588c25083d97b640319dff076e884c6b661a4e37eb97361c5b9845fafcd1ef0958c34f83865b44fd7","feeNQT":0,"type":3,"version":1,"ecBlockId":"9110437482347234720","attachment":{"input":[1365308818,-704527682,-70936512],"version.PiggybackedProofOfWork":1,"id":"11341360148518111736"},"subtype":2,"amountNQT":1000000000,"recipient":"12808828738982832951","ecBlockHeight":2243,"deadline":1440,"timestamp":21237055}
java.lang.RuntimeException: Proof of work is invalid: causes ElasticPL function to crash
at nxt.WorkLogicManager.validatePOW(WorkLogicManager.java:1204)
at nxt.TransactionType$WorkControl$4.validateAttachment(TransactionType.java:661)
at nxt.Attachment$AbstractAttachment.validate(Attachment.java:34)
at nxt.TransactionImpl.validate(TransactionImpl.java:835)
at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:468)
at nxt.TransactionProcessorImpl.access$8(TransactionProcessorImpl.java:440)
at nxt.TransactionProcessorImpl$5.run(TransactionProcessorImpl.java:211)
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-02 23:43:20 FINE: TransactionProcessorImpl.processPeerTransactions: Invalid transaction from peer: {"senderPublicKey":"ae0df06215caa34bf680a84b24330554d0af092b925b5bcf8704ac31cd489019","signature":"74577f9d208e5119e48772a394f7aa255b1895434a876d21b47d0466039c450770031c9f41adee104bc539786d0ea3dba62f03eed82d78f5d5dd7f3e073ca537","feeNQT":0,"type":3,"version":1,"ecBlockId":"2573426999249322481","attachment":{"input":[-658827307,-1689579444,1999346988],"version.PiggybackedProofOfWork":1,"id":"4210165941331695358"},"subtype":2,"amountNQT":1000000000,"recipient":"12808828738982832951","ecBlockHeight":2242,"deadline":1440,"timestamp":21236979}
nxt.NxtException$NotValidException: Cannot submit POW for an already cancelled or finished work
at nxt.TransactionType$WorkControl$4.validateAttachment(TransactionType.java:641)
at nxt.Attachment$AbstractAttachment.validate(Attachment.java:34)
at nxt.TransactionImpl.validate(TransactionImpl.java:835)
at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:468)
at nxt.TransactionProcessorImpl.access$8(TransactionProcessorImpl.java:440)
at nxt.TransactionProcessorImpl$5.run(TransactionProcessorImpl.java:211)
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)
java.lang.RuntimeException: Proof of work is invalid: does not meet target
at nxt.WorkLogicManager.validatePOW(WorkLogicManager.java:1199)
at nxt.TransactionType$WorkControl$4.validateAttachment(TransactionType.java:661)
at nxt.Attachment$AbstractAttachment.validate(Attachment.java:34)
at nxt.TransactionImpl.validate(TransactionImpl.java:835)
at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:468)
at nxt.TransactionProcessorImpl.access$8(TransactionProcessorImpl.java:440)
at nxt.TransactionProcessorImpl$5.run(TransactionProcessorImpl.java:211)
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-02 23:43:20 FINE: TransactionProcessorImpl.processPeerTransactions: Invalid transaction from peer: {"senderPublicKey":"ae0df06215caa34bf680a84b24330554d0af092b925b5bcf8704ac31cd489019","signature":"0fa10e53673f40371caa1afd80464175fd6db42a735f673e80a94e026a5e5d03772eeccdfd72d7292c130d4c5053c08b638406c7a8ee203afbcbf3504e8542cb","feeNQT":0,"type":3,"version":1,"ecBlockId":"12998068690024528804","attachment":{"input":[-558658430,-1424419223,-684303585],"version.PiggybackedProofOfWork":1,"id":"11341360148518111736"},"subtype":2,"amountNQT":1000000000,"recipient":"12808828738982832951","ecBlockHeight":2244,"deadline":1440,"timestamp":21237106}
java.lang.RuntimeException: Proof of work is invalid: causes ElasticPL function to crash
at nxt.WorkLogicManager.validatePOW(WorkLogicManager.java:1204)
at nxt.TransactionType$WorkControl$4.validateAttachment(TransactionType.java:661)
at nxt.Attachment$AbstractAttachment.validate(Attachment.java:34)
at nxt.TransactionImpl.validate(TransactionImpl.java:835)
at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:468)
at nxt.TransactionProcessorImpl.access$8(TransactionProcessorImpl.java:440)
at nxt.TransactionProcessorImpl$5.run(TransactionProcessorImpl.java:211)
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)
Validating POW for work = -7105383925191439880
Validating POW for work = -7105383925191439880
java.lang.RuntimeException: Proof of work is invalid: does not meet target

I will have a more detailed look tomorrow morning, I hope nobody is worried, this is expected behaviour! We need to identify all side cases and all glitches that may be possible. Unvoid, thank you so much for helping out! I am sure that you will be rewarded hugely.

The problem currently obviously lies in the block generation routine.

If you take a look at this function (nxt.BlockchainProcessorImpl.generateBlock(BlockchainProcessorImpl.java:958)), you see it somehow includes invalid work. Not sure why invalid work even got included into the mempool in the first place. Maybe it got accepted first, then not included in any block, and then became invalid due to changed difficulty. Everything that is in the mempool should be accepted in a block in the first place!!! There is a bug somewhere! Clearly.

Code:
java.lang.RuntimeException: Proof of work is invalid: does not meet target
at nxt.WorkLogicManager.validatePOW(WorkLogicManager.java:1199)
at nxt.TransactionType$WorkControl$4.validateAttachment(TransactionType.java:661)
at nxt.Attachment$AbstractAttachment.validate(Attachment.java:34)
at nxt.TransactionImpl.validate(TransactionImpl.java:835)
at nxt.BlockchainProcessorImpl.generateBlock(BlockchainProcessorImpl.java:958)
at nxt.Generator.forge(Generator.java:296)
at nxt.Generator$1.run(Generator.java:79)
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-02 23:55:21 FINE: Generator$1.run: Error in block generation thread

I would say, if you can fix this mistake before my holiday is over I would give you 5 BTC of my personal savings on top of the bug bounties that Lannister will pay out to you.
trader19
Legendary
*
Offline Offline

Activity: 1232
Merit: 1001



View Profile WWW
September 02, 2016, 10:08:57 PM
 #1524

Wow, unvoid! It looks like you have found just another glitch! I think Lannister would send you 2 more BTC (as I recall you are eligible for the first bug bounty as well)
....
I would say, if you can fix this mistake before my holiday is over I would give you 5 BTC of my personal savings on top of the bug bounties that Lannister will pay out to you.
yes i have the same on my logs, when i was setting up second server it throwed alot of errors and banned all the peers.. can this be the reason that network stoped moving??

Edit: i must admit i played a bit with ports on second node i setuped, may be that triggered me banning other nodes. change i made were on  nxt-default.properties!! it could be a problem with how peers interact.

here my log maybe it helps:
Code:
2016-09-03 00:03:58 FINE: TransactionProcessorImpl.processPeerTransactions: Invalid transaction from peer: {"senderPublicKey":"ae0df06215caa34bf680a84b24330554d0af092b925b5bcf8704ac31cd489019","signature":"184ab92b3d18eb8b6dc426415c8fd47c471db184e7ec743ba6b54f3e7358d901d8245682f92285baae65db3df9b6c795b72ccaf58a9c152acba825147c20f9da","feeNQT":0,"type":3,"version":1,"ecBlockId":"2871771636556869817","attachment":{"input":[179229214,1466908374,1493491762],"version.PiggybackedProofOfWork":1,"id":"11341360148518111736"},"subtype":2,"amountNQT":1000000000,"recipient":"12808828738982832951","ecBlockHeight":2258,"deadline":1440,"timestamp":21238027}
java.lang.RuntimeException: Proof of work is invalid: causes ElasticPL function to crash
        at nxt.WorkLogicManager.validatePOW(WorkLogicManager.java:1204)
        at nxt.TransactionType$WorkControl$4.validateAttachment(TransactionType.java:661)
        at nxt.Attachment$AbstractAttachment.validate(Attachment.java:34)
        at nxt.TransactionImpl.validate(TransactionImpl.java:835)
        at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:468)
        at nxt.TransactionProcessorImpl.access$500(TransactionProcessorImpl.java:36)
        at nxt.TransactionProcessorImpl$5.run(TransactionProcessorImpl.java:211)
        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)
Validating POW for work = -7105383925191439880
java.lang.RuntimeException: Proof of work is invalid: does not meet target
        at nxt.WorkLogicManager.validatePOW(WorkLogicManager.java:1199)
        at nxt.TransactionType$WorkControl$4.validateAttachment(TransactionType.java:661)
        at nxt.Attachment$AbstractAttachment.validate(Attachment.java:34)
        at nxt.TransactionImpl.validate(TransactionImpl.java:835)
        at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:468)
        at nxt.TransactionProcessorImpl.access$500(TransactionProcessorImpl.java:36)
        at nxt.TransactionProcessorImpl$5.run(TransactionProcessorImpl.java:211)
        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-03 00:03:58 FINE: TransactionProcessorImpl.processPeerTransactions: Invalid transaction from peer: {"senderPublicKey":"ae0df06215caa34bf680a84b24330554d0af092b925b5bcf8704ac31cd489019","signature":"ab35345f8fd915a8271e3e42e453eae978fb381f42e08add99f960d920ae90077709ee289768548661d2e8fbad93e5e49fa73810e94c51e8a2a3be02e571bc55","feeNQT":0,"type":3,"version":1,"ecBlockId":"8374719821771097422","attachment":{"input":[-927207464,-1246912258,1665854923],"version.PiggybackedProofOfWork":1,"id":"11341360148518111736"},"subtype":2,"amountNQT":1000000000,"recipient":"12808828738982832951","ecBlockHeight":2260,"deadline":1440,"timestamp":21238093}
java.lang.RuntimeException: Proof of work is invalid: causes ElasticPL function to crash
        at nxt.WorkLogicManager.validatePOW(WorkLogicManager.java:1204)
        at nxt.TransactionType$WorkControl$4.validateAttachment(TransactionType.java:661)
        at nxt.Attachment$AbstractAttachment.validate(Attachment.java:34)
        at nxt.TransactionImpl.validate(TransactionImpl.java:835)
        at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:468)
        at nxt.TransactionProcessorImpl.access$500(TransactionProcessorImpl.java:36)
        at nxt.TransactionProcessorImpl$5.run(TransactionProcessorImpl.java:211)
        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)
Validating POW for work = -7105383925191439880
java.lang.RuntimeException: Proof of work is invalid: does not meet target
        at nxt.WorkLogicManager.validatePOW(WorkLogicManager.java:1199)
        at nxt.TransactionType$WorkControl$4.validateAttachment(TransactionType.java:661)
        at nxt.Attachment$AbstractAttachment.validate(Attachment.java:34)
        at nxt.TransactionImpl.validate(TransactionImpl.java:835)
        at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:468)
        at nxt.TransactionProcessorImpl.access$500(TransactionProcessorImpl.java:36)
        at nxt.TransactionProcessorImpl$5.run(TransactionProcessorImpl.java:211)
        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-03 00:03:58 FINE: TransactionProcessorImpl.processPeerTransactions: Invalid transaction from peer: {"senderPublicKey":"ae0df06215caa34bf680a84b24330554d0af092b925b5bcf8704ac31cd489019","signature":"750e00d1d840a09a7917a519653f1f58fe7af2f5f8e6fc2fe1010ba285420801e748c8dd1f0cfacac89b80b9f3ed2d7eee4483b8cb7bec7438f9bb807bd3980b","feeNQT":0,"type":3,"version":1,"ecBlockId":"8374719821771097422","attachment":{"input":[-243064765,-1325190373,-329177223],"version.PiggybackedProofOfWork":1,"id":"11341360148518111736"},"subtype":2,"amountNQT":1000000000,"recipient":"12808828738982832951","ecBlockHeight":2260,"deadline":1440,"timestamp":21238095}
java.lang.RuntimeException: Proof of work is invalid: causes ElasticPL function to crash
        at nxt.WorkLogicManager.validatePOW(WorkLogicManager.java:1204)
        at nxt.TransactionType$WorkControl$4.validateAttachment(TransactionType.java:661)
        at nxt.Attachment$AbstractAttachment.validate(Attachment.java:34)
        at nxt.TransactionImpl.validate(TransactionImpl.java:835)
        at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:468)
        at nxt.TransactionProcessorImpl.access$500(TransactionProcessorImpl.java:36)
        at nxt.TransactionProcessorImpl$5.run(TransactionProcessorImpl.java:211)
        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)
Validating POW for work = -7105383925191439880
java.lang.RuntimeException: Proof of work is invalid: does not meet target
        at nxt.WorkLogicManager.validatePOW(WorkLogicManager.java:1199)
        at nxt.TransactionType$WorkControl$4.validateAttachment(TransactionType.java:661)
        at nxt.Attachment$AbstractAttachment.validate(Attachment.java:34)
        at nxt.TransactionImpl.validate(TransactionImpl.java:835)
        at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:468)
        at nxt.TransactionProcessorImpl.access$500(TransactionProcessorImpl.java:36)
        at nxt.TransactionProcessorImpl$5.run(TransactionProcessorImpl.java:211)
        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-03 00:03:58 FINE: TransactionProcessorImpl.processPeerTransactions: Invalid transaction from peer: {"senderPublicKey":"ae0df06215caa34bf680a84b24330554d0af092b925b5bcf8704ac31cd489019","signature":"23efd6d0f5d475a7bacbff1712cf47e59a17ca838854ccf9806bea12e3482f0c607f32f146a67530c957fa83da96d810d81760f62f8330464e00063bba97255b","feeNQT":0,"type":3,"version":1,"ecBlockId":"9625735294777976311","attachment":{"input":[-296756662,298707674,763600244],"version.PiggybackedProofOfWork":1,"id":"11341360148518111736"},"subtype":2,"amountNQT":1000000000,"recipient":"12808828738982832951","ecBlockHeight":2261,"deadline":1440,"timestamp":21238123}
java.lang.RuntimeException: Proof of work is invalid: causes ElasticPL function to crash
        at nxt.WorkLogicManager.validatePOW(WorkLogicManager.java:1204)
        at nxt.TransactionType$WorkControl$4.validateAttachment(TransactionType.java:661)
        at nxt.Attachment$AbstractAttachment.validate(Attachment.java:34)
        at nxt.TransactionImpl.validate(TransactionImpl.java:835)
        at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:468)
        at nxt.TransactionProcessorImpl.access$500(TransactionProcessorImpl.java:36)
        at nxt.TransactionProcessorImpl$5.run(TransactionProcessorImpl.java:211)
        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)
Validating POW for work = -7105383925191439880
java.lang.RuntimeException: Proof of work is invalid: does not meet target
        at nxt.WorkLogicManager.validatePOW(WorkLogicManager.java:1199)
        at nxt.TransactionType$WorkControl$4.validateAttachment(TransactionType.java:661)
        at nxt.Attachment$AbstractAttachment.validate(Attachment.java:34)
        at nxt.TransactionImpl.validate(TransactionImpl.java:835)
        at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:468)
        at nxt.TransactionProcessorImpl.access$500(TransactionProcessorImpl.java:36)
        at nxt.TransactionProcessorImpl$5.run(TransactionProcessorImpl.java:211)
        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-03 00:03:58 FINE: TransactionProcessorImpl.processPeerTransactions: Invalid transaction from peer: {"senderPublicKey":"ae0df06215caa34bf680a84b24330554d0af092b925b5bcf8704ac31cd489019","signature":"531eb1490e04eefe9e9ac0992fa44cc4d2d412fba9d6780b3638597aad8e5307eb30c676d2a9f6363a2adba7cde6d5154fd3e416c5e837fb93c019bb840301bf","feeNQT":0,"type":3,"version":1,"ecBlockId":"7943361064250860785","attachment":{"input":[-990667952,654208454,-2008405028],"version.PiggybackedProofOfWork":1,"id":"11341360148518111736"},"subtype":2,"amountNQT":1000000000,"recipient":"12808828738982832951","ecBlockHeight":2282,"deadline":1440,"timestamp":21239436}
java.lang.RuntimeException: Proof of work is invalid: causes ElasticPL function to crash
        at nxt.WorkLogicManager.validatePOW(WorkLogicManager.java:1204)
        at nxt.TransactionType$WorkControl$4.validateAttachment(TransactionType.java:661)
        at nxt.Attachment$AbstractAttachment.validate(Attachment.java:34)
        at nxt.TransactionImpl.validate(TransactionImpl.java:835)
        at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:468)
        at nxt.TransactionProcessorImpl.access$500(TransactionProcessorImpl.java:36)
        at nxt.TransactionProcessorImpl$5.run(TransactionProcessorImpl.java:211)
        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-03 00:03:58 FINE: PeerImpl.blacklist: Blacklisting 52.28.123.208 because of: nxt.NxtException$NotValidException: Peer sends invalid transactions
nxt.NxtException$NotValidException: Peer sends invalid transactions
        at nxt.TransactionProcessorImpl.processPeerTransactions(TransactionProcessorImpl.java:495)
        at nxt.TransactionProcessorImpl.access$500(TransactionProcessorImpl.java:36)
        at nxt.TransactionProcessorImpl$5.run(TransactionProcessorImpl.java:211)
        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)

also getting bunch of this since network frozen:
Code:
Clearing inactive listener: 383971131
Clearing inactive listener: 383971131
Clearing inactive listener: 383971131
Clearing inactive listener: 383971131
Clearing inactive listener: 383971131
Clearing inactive listener: 383971131
Clearing inactive listener: 383971131
Clearing inactive listener: 383971131
Clearing inactive listener: 383971131
Clearing inactive listener: 383971131
Clearing inactive listener: 383971131
Clearing inactive listener: 383971131
Clearing inactive listener: 383971131

Join the Elastic revolution!  Elastic - The Decentralized Supercomputer
ELASTIC WEBSITE | NEW ANNOUNCEMENT THREAD | ELASTIC SLACK | ELASTIC FORUM
Evil-Knievel
Legendary
*
Offline Offline

Activity: 1204
Merit: 1149



View Profile
September 03, 2016, 06:26:04 AM
 #1525

Never mind, I think I have fixed the mistake!

The problem was, that the work cancellation transaction threw a "RuntimeException" when they were invalid. Usually invalid ones get dropped from the memory pool immediately (we should think about why that didn't happen here? Maybe you mined with two different computers?). In this case they all were in the mempool.

This should be no problem, because the blockGeneration should ignore them. But it didn't do it, because it only ignored TX with an Exception type of "NotValidException".

Quote
try {
                    unconfirmedTransaction.getTransaction().validate();
} catch (NxtException.NotCurrentlyValidException e) {
                    continue;
} catch (NxtException.ValidationException e) {
                    transactionProcessor.removeUnconfirmedTransaction(unconfirmedTransaction.getTransaction());
                    continue;
}

So its important we make sure that all transactions that invalidate give back a NotValidTransaction! (TODO to myself)

Block 2317 was just mined!

One Problem that still might occur is that the old corrupt TX are in the mempool and are trying to be broadcasted which may get you blacklisted by the two public peers. We have to think about a solution for that!

I think, git pull, deleting nxt_test_db/, doing a compile.sh and a run.sh should be enough to clear the mempool and redownload the blockchain from the "fixed" nodes. The chain was not reset.


I still have no idea why invalid transactions are broadcast?! I am mobile at the moment and do not always have internet access! If someone finds out, and provides a fix I would give 2 BTC of my own savings as a bonus for the help.


Evil-Knievel
Legendary
*
Offline Offline

Activity: 1204
Merit: 1149



View Profile
September 03, 2016, 06:26:36 AM
 #1526

We need more crashes!  Wink
Thank you all for stress-testing! Every crash in this phase is a good crash!
unvoid
Hero Member
*****
Offline Offline

Activity: 535
Merit: 500



View Profile
September 03, 2016, 04:34:16 PM
 #1527

@EK awesome. Another step to XEL maturity.

Blockchain explorer on it's way.


BTC: 1CMgHWx4wkAaAy2FfeCyPdedUExmhGhfi5
XEL: XEL-HCM8-KB6E-YFLK-8BWMF
StratisKing
Hero Member
*****
Offline Offline

Activity: 756
Merit: 511


View Profile
September 03, 2016, 05:09:40 PM
 #1528

We need more crashes!  Wink
Thank you all for stress-testing! Every crash in this phase is a good crash!

Yrp, crashing in test-net is 100% good things, to avoid bug in main-net running, crashing befote main-net live is an improvement of this project.
unvoid
Hero Member
*****
Offline Offline

Activity: 535
Merit: 500



View Profile
September 03, 2016, 05:20:03 PM
 #1529

@ImI is there any problem with your node? I'm mining all blocks since 30min.

BTC: 1CMgHWx4wkAaAy2FfeCyPdedUExmhGhfi5
XEL: XEL-HCM8-KB6E-YFLK-8BWMF
ImI
Legendary
*
Offline Offline

Activity: 1876
Merit: 1008



View Profile
September 03, 2016, 05:25:33 PM
 #1530

@ImI is there any problem with your node? I'm mining all blocks since 30min.

i'll check

edit: http://ec2-52-28-123-208.eu-central-1.compute.amazonaws.com:6876/index.html seems down.

so far i havent upgraded my own vps-node to 0.2.0 and therefore you are running the network now. good that we are now past those 1440 blocks so you are able to forge.

i will update my node as soon as i have a little free time and then start forging again. or maybe aws will come back online soon anyway.
unvoid
Hero Member
*****
Offline Offline

Activity: 535
Merit: 500



View Profile
September 03, 2016, 05:51:26 PM
 #1531

Good. Thanks for checking. Hope your node will be live soon. Anyway, it's forging time for anyone else guys! Anyone who has 100k XEL can forge a block quite fast Smiley

If you want to try XEL:

Download testnet client https://github.com/OrdinaryDude/elastic-reference-client watch this video for instructions how to run it https://player.vimeo.com/video/178616474?quality=1080p and paste your address here to receive some XEL for testing and fun.

BTC: 1CMgHWx4wkAaAy2FfeCyPdedUExmhGhfi5
XEL: XEL-HCM8-KB6E-YFLK-8BWMF
BigBoom3599
Sr. Member
****
Offline Offline

Activity: 406
Merit: 250


View Profile
September 03, 2016, 06:19:09 PM
 #1532

Maybe for the next version of the testnet there should be a better to distribute XELs, because only a couple of people are able to forge atm.
ImI
Legendary
*
Offline Offline

Activity: 1876
Merit: 1008



View Profile
September 03, 2016, 06:22:33 PM
 #1533

Maybe for the next version of the testnet there should be a better to distribute XELs, because only a couple of people are able to forge atm.

just post your address and we send you some. np.

edit: and as the big stack isnt forging at the moment it should be quite easy to forge now.

edit2: if you want to run a 24/7 vps you will obv get a good chunk
BigBoom3599
Sr. Member
****
Offline Offline

Activity: 406
Merit: 250


View Profile
September 03, 2016, 06:38:40 PM
 #1534

Maybe for the next version of the testnet there should be a better to distribute XELs, because only a couple of people are able to forge atm.

just post your address and we send you some. np.

edit: and as the big stack isnt forging at the moment it should be quite easy to forge now.

edit2: if you want to run a 24/7 vps you will obv get a good chunk
XEL-XD24-CTKL-DT3K-DGF25 here it is Smiley
unvoid
Hero Member
*****
Offline Offline

Activity: 535
Merit: 500



View Profile
September 03, 2016, 06:49:32 PM
 #1535

Maybe for the next version of the testnet there should be a better to distribute XELs, because only a couple of people are able to forge atm.

There is no problem with distribution. Main problem here is that no one who is willing to run full 24/7 node is asking for test XEL.

If you asking for test XEL and you know that you will run full node (forging), up for 24/7 let us know. @ImI will send you x10 (than normal) more coins then.

BTC: 1CMgHWx4wkAaAy2FfeCyPdedUExmhGhfi5
XEL: XEL-HCM8-KB6E-YFLK-8BWMF
unvoid
Hero Member
*****
Offline Offline

Activity: 535
Merit: 500



View Profile
September 03, 2016, 06:52:07 PM
 #1536

If you want to try XEL:

Download testnet client https://github.com/OrdinaryDude/elastic-reference-client watch this video for instructions how to run it https://player.vimeo.com/video/178616474?quality=1080p and paste your address here to receive some XEL for testing and fun.

BTC: 1CMgHWx4wkAaAy2FfeCyPdedUExmhGhfi5
XEL: XEL-HCM8-KB6E-YFLK-8BWMF
Evil-Knievel
Legendary
*
Offline Offline

Activity: 1204
Merit: 1149



View Profile
September 03, 2016, 08:49:48 PM
 #1537

By the way, there is an old node broadcasting bad transactions and getting blacklisted frequently. An update (git pull & compile) should help @   108.61.177.169   
cryptodv
Hero Member
*****
Offline Offline

Activity: 882
Merit: 501


btcstakes.com


View Profile WWW
September 03, 2016, 09:15:09 PM
 #1538

Need help with XEL distribution, trying to contact Lannister but his PM is blocked.  Undecided

            ▄▄████▄▄
        ▄▄██████████████▄▄
      ███████████████████████▄▄
      ▀▀█████████████████████████
██▄▄       ▀▀█████████████████████
██████▄▄        ▀█████████████████
███████████▄▄       ▀▀████████████
███████████████▄▄        ▀████████
████████████████████▄▄       ▀▀███
 ▀▀██████████████████████▄▄
     ▀▀██████████████████████▄▄
▄▄        ▀██████████████████████▄
████▄▄        ▀▀██████████████████
█████████▄▄        ▀▀█████████████
█████████████▄▄        ▀▀█████████
██████████████████▄▄        ▀▀████
▀██████████████████████▄▄
  ▀▀████████████████████████
      ▀▀█████████████████▀▀
           ▀▀███████▀▀



.SEMUX
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
  Semux uses .100% original codebase.
  Superfast with .30 seconds instant finality.
  Tested .5000 tx per block. on open network
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
Evil-Knievel
Legendary
*
Offline Offline

Activity: 1204
Merit: 1149



View Profile
September 03, 2016, 09:18:57 PM
 #1539

Need help with XEL distribution, trying to contact Lannister but his PM is blocked.  Undecided

https://bitmsg.me
BM-2cXXoFkRtXKvV4oiJcJjBXyYBiqo8Eibmc
trader19
Legendary
*
Offline Offline

Activity: 1232
Merit: 1001



View Profile WWW
September 03, 2016, 09:36:41 PM
 #1540

By the way, there is an old node broadcasting bad transactions and getting blacklisted frequently. An update (git pull & compile) should help @   108.61.177.169   
thx for heads up, i will update asap  Wink

Join the Elastic revolution!  Elastic - The Decentralized Supercomputer
ELASTIC WEBSITE | NEW ANNOUNCEMENT THREAD | ELASTIC SLACK | ELASTIC FORUM
Pages: « 1 ... 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 [77] 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 ... 347 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!