[ANN][XEL] Elastic Project - The Decentralized Supercomputer - page 96.

coralreefer

sr. member

Activity: 464

Merit: 260

Quote from: Evil-Knievel on April 11, 2017, 03:38:08 PM

Is queuing the right way to go at all?

I don't really see any way around it, but maybe some other bright minds around here can come up with a solution.

But the bottom line is we can easily have complex jobs that take considerable time to solve, and each submission would need to be validated. For example, if I create a job that takes 0.1 sec to solve, and I dump 1000 submissions onto a SN, that node would be tied up for 2 minutes before it could do anything else. And this will take place while people are dumping hundreds if not thousands of legitimate POW submissions on the SN.

I still don't know of a good solution...I still wish we didn't have POW in xel and just focused on bounties. I know you'll say we need the POW logic ;-) I'm just not convinced, and I feel like it just complicates the validation / targetting / volume issues.

Evil-Knievel

legendary

Activity: 1260

Merit: 1168

Quote from: coralreefer on April 11, 2017, 03:04:18 PM

Quote from: Evil-Knievel on April 11, 2017, 12:39:27 PM

Just thinking out loud: do we really need the bounty announcements in the new SN scheme?

It depends on how well the SN can handle a huge volume of submissions...but I believe it will have to do this either way.

Yesterday, I submitted a job that had an issue which allowed every pass of the interpreter to find a "Bounty", so the miner tried to send hundreds of submissions pretty quickly....this is something anyone could do (i.e. create a simple job that allows legitimate bounty submissions to spam the SN).

So I thought your original design had a small fee on each of these submissions, along with the announcement in order to deter this kind of behaviour. But if you have another approach that simplifies things, I'd be all for it.

Well, first of all a job has a natural bounty limit ... submissions beyond this level are not permitted. But of course, there is a grace period between the submissions and their actual inclusion in the blockchain (or its unconfirmed transaction cache). In this time window it is possible to flood as much as you can. We could add a "SN rate limit" which would allow not more than x transactions per node per second.

What sucks more is the lack of direct feedback from the SN. Since we queue at the moment, the miner does not even know if his submission was dropped, accepted or denied. We really have to think this through! Is queuing the right way to go at all?

Btw: I could reproduce your bug today. I just could not yet find out why it happens.

coralreefer

sr. member

Activity: 464

Merit: 260

Quote from: Evil-Knievel on April 11, 2017, 12:39:27 PM

Just thinking out loud: do we really need the bounty announcements in the new SN scheme?

It depends on how well the SN can handle a huge volume of submissions...but I believe it will have to do this either way.

Yesterday, I submitted a job that had an issue which allowed every pass of the interpreter to find a "Bounty", so the miner tried to send hundreds of submissions pretty quickly....this is something anyone could do (i.e. create a simple job that allows legitimate bounty submissions to spam the SN).

So I thought your original design had a small fee on each of these submissions, along with the announcement in order to deter this kind of behaviour. But if you have another approach that simplifies things, I'd be all for it.

unvoid

hero member

Activity: 535

Merit: 500

@EK we are in deep need to prepare nice Windows install for people. Take a look at this:

unvoid

hero member

Activity: 535

Merit: 500

Forum stats from last 24h by google analytics.

unvoid

hero member

Activity: 535

Merit: 500

IMO bad idea. We don't need to reduce any block creation. We already have quite fast block creation time (IMO too fast). Block creation is fine, I can't see any reason to decrease time (even for testnet).

MostlyGhostly

full member

Activity: 398

Merit: 110

Quote from: jioy on April 10, 2017, 06:57:11 AM

Quote from: by rallier on April 09, 2017, 02:17:44 PM

@EK: We can block time reduced to 30 sec for testing purposes. we never see what happens on 30k blocks
btw, pls import my last changes to repos

reduce block time for test is a good advice Grin

Dont listen to him. Increase block time to 2 minutes and put it on mainnet, u dont even need to test it. 2 min is ideal if u seek a trade-off between security and transaction propagation time. Reducing the block time will lead to the possibility of massive microtx spam. Tx fee is ridiculously low atm making spam attacks cheaper than ever before.

unvoid

hero member

Activity: 535

Merit: 500

@EK

For me it's big lack of clarity. Please response and explain why we don't have any log file since long time.

https://talk.elasticexplorer.org/t/what-happened-with-logs/98

unvoid

hero member

Activity: 535

Merit: 500

Quote from: Evil-Knievel on April 11, 2017, 12:39:27 PM

Just thinking out loud: do we really need the bounty announcements in the new SN scheme?

It depends what is "new SN scheme". But perhaps only you and @coralreefer know.

Evil-Knievel

legendary

Activity: 1260

Merit: 1168

Just thinking out loud: do we really need the bounty announcements in the new SN scheme?

by rallier

legendary

Activity: 1848

Merit: 1334

just in case

@EK:
I created Elastic-Coin github organization. my suggestion we can work repos on this organization. I invited you with admin privileges.
https://github.com/elastic-coin

We can add to more people and we can share to jobs .
If you accept invite, you should start push to elastic-coin repo. We will update all links to this organization url.
I will use release tags from your commits & i will update docker side @github.

Evil-Knievel

legendary

Activity: 1260

Merit: 1168

@coralreefer: Thanks for the first test. Yes, the corrupt jobs are a pseudo-SN thing, I will have it fixed this night.
Also, I will take a look into the bug you'be posted.

One big problem about the SN scheme is, that it'S "best effort". You will not notice when a SN has not relayed your submission (because it does not want to or because it's wrong). Maybe we should think about some kind of feedback mechanism. This has to be well thought of because SN do queue things and do not have to reply immediately.

I will make a flow chart to illustrate that problem later on.

coralreefer

sr. member

Activity: 464

Merit: 260

EK, I've noticed a couple things running the miner against the testnet:

1) Without SN logic to validate the ElasticPL, authors can upload corrupt jobs. There is one out there right now...so I added a temp fix to the miner to ignore these.

2) We will need to revisit the starting Target, maybe base it on WCET. I mined a slow job like the TSP example and got no POW in 5 minutes of mining due to the low hashrate on a complex job...and because I got no POW, the server had no idea I was there and didn't lower the target.

3) Next I switched over to a simple/meaningless job.

Code:

if((m[7] >= 0) && (m[7] <= 100)) {
m[20] = 10;
m[21] = 20;
}
else {
m[20] = 11;
m[21] = 21;
}
verify (m[20]==10);

Everything from the miner side looked fine, but after a minute or so the connections dropped and I got the following errors:

Code:

2017-04-10 20:52:29 INFO: TransactionProcessorImpl.broadcast: [SIGN] Broadcasting TX: 03128d3e5a060300964be53db0cc61dd465fa765b03651c1bb06c7ce6b738be739ee1f143ea1910f00000000000000000000000000000000000000000000000000000000000000006ba66909eaf365ed000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000df8a6383b405544ab1e1993a33c93c4e6b55069bdab452d31b31a337a0a0ed011804f9c8c5c225fa8d9061fd4d8b61469937d8d8bc54cbc675260d762a716a26000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000084040000a14dc6f5db4bd72d016f6f66040bb86a0000000000000000009612de05000000000000000000000000b00b98907de4a706
2017-04-10 20:52:29 INFO: TransactionProcessorImpl.broadcast: Transaction 2515125811393853397 is relayed to SN.
2017-04-10 20:52:31 INFO: TransactionImpl.: [SIGN] Signing HEX: 03128f3e5a060300964be53db0cc61dd465fa765b03651c1bb06c7ce6b738be739ee1f143ea1910f00000000000000000000000000000000000000000000000000000000000000006ba66909eaf365ed00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000084040000a14dc6f5db4bd72d016f6f66040bb86a000000000000000000c7eaf6050000000000000000000000009967565d7cb599bc
Json Trans.: {"senderPublicKey":"964be53db0cc61dd465fa765b03651c1bb06c7ce6b738be739ee1f143ea1910f","attachment":{"version.PiggybackedProofOfWork":1,"id":"30038704989302639","multiplicator":"c7eaf6050000000000000000000000009967565d7cb599bc"},"subtype":2,"amountNQT":0,"signature":"808b4f02ce59eb488a8592f080a62c9bbd0eed2fe1dc8ba9a24b83274bbe9602fd144a59ced55a871dc00a32595745dfe06e7ba48d8ff68bb7be940c3725c9f0","feeNQT":0,"ecBlockHeight":1156,"type":3,"deadline":3,"version":1,"timestamp":106577551,"ecBlockId":"3303192259792883105"}
Trans. IDNR: 7604604596790863556
2017-04-10 20:52:31 INFO: TransactionProcessorImpl.broadcast: [SIGN] Broadcasting TX: 03128f3e5a060300964be53db0cc61dd465fa765b03651c1bb06c7ce6b738be739ee1f143ea1910f00000000000000000000000000000000000000000000000000000000000000006ba66909eaf365ed000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000808b4f02ce59eb488a8592f080a62c9bbd0eed2fe1dc8ba9a24b83274bbe9602fd144a59ced55a871dc00a32595745dfe06e7ba48d8ff68bb7be940c3725c9f0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000084040000a14dc6f5db4bd72d016f6f66040bb86a000000000000000000c7eaf6050000000000000000000000009967565d7cb599bc
2017-04-10 20:52:31 INFO: TransactionProcessorImpl.broadcast: Transaction 7604604596790863556 is relayed to SN.
2017-04-10 20:52:37 INFO: TransactionImpl.: [SIGN] Signing HEX: 0312963e5a060300964be53db0cc61dd465fa765b03651c1bb06c7ce6b738be739ee1f143ea1910f00000000000000000000000000000000000000000000000000000000000000006ba66909eaf365ed00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000084040000a14dc6f5db4bd72d016f6f66040bb86a0000000000000000007d043e06000000000000000000000000a000d204b55614ae
Json Trans.: {"senderPublicKey":"964be53db0cc61dd465fa765b03651c1bb06c7ce6b738be739ee1f143ea1910f","attachment":{"version.PiggybackedProofOfWork":1,"id":"30038704989302639","multiplicator":"7d043e06000000000000000000000000a000d204b55614ae"},"subtype":2,"amountNQT":0,"signature":"5bc35c3c89ed59de5ab955a0f6de4ce91ad585201727bedce09f137e9e43e102e7f2d7ea576f28416ff0b1c2985fea1e51d1f6399615af49ce1e89cc71e14e92","feeNQT":0,"ecBlockHeight":1156,"type":3,"deadline":3,"version":1,"timestamp":106577558,"ecBlockId":"3303192259792883105"}
Trans. IDNR: 13246459442309955219
2017-04-10 20:52:37 INFO: TransactionProcessorImpl.broadcast: [SIGN] Broadcasting TX: 0312963e5a060300964be53db0cc61dd465fa765b03651c1bb06c7ce6b738be739ee1f143ea1910f00000000000000000000000000000000000000000000000000000000000000006ba66909eaf365ed0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000005bc35c3c89ed59de5ab955a0f6de4ce91ad585201727bedce09f137e9e43e102e7f2d7ea576f28416ff0b1c2985fea1e51d1f6399615af49ce1e89cc71e14e92000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000084040000a14dc6f5db4bd72d016f6f66040bb86a0000000000000000007d043e06000000000000000000000000a000d204b55614ae
2017-04-10 20:52:37 INFO: TransactionProcessorImpl.broadcast: Transaction 13246459442309955219 is relayed to SN.
2017-04-10 20:52:45 INFO: TransactionImpl.: [SIGN] Signing HEX: 03149d3e5a060300964be53db0cc61dd465fa765b03651c1bb06c7ce6b738be739ee1f143ea1910f00000000000000000000000000000000000000000000000000000000000000006ba66909eaf365ed00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000084040000a14dc6f5db4bd72d016f6f66040bb86a00210000b4f95365e8fb345e357c35bcc4e58cc99015759ce5fee19701b51096f0494baf
Json Trans.: {"senderPublicKey":"964be53db0cc61dd465fa765b03651c1bb06c7ce6b738be739ee1f143ea1910f","attachment":{"version.PiggybackedProofOfBountyAnnouncement":1,"id":"30038704989302639","hash_announced":"b4f95365e8fb345e357c35bcc4e58cc99015759ce5fee19701b51096f0494baf"},"subtype":4,"amountNQT":0,"signature":"35696b86aba0e633fae00852d0022899b769cbd8f6eaf3059246669342f600006b5bcc2b578c10c5a89464179da2999eb71e0a9d554fb33eb70a30c4e4df71f5","feeNQT":0,"ecBlockHeight":1156,"type":3,"deadline":3,"version":1,"timestamp":106577565,"ecBlockId":"3303192259792883105"}
Trans. IDNR: 9573744148325208918
2017-04-10 20:52:45 INFO: TransactionProcessorImpl.broadcast: [SIGN] Broadcasting TX: 03149d3e5a060300964be53db0cc61dd465fa765b03651c1bb06c7ce6b738be739ee1f143ea1910f00000000000000000000000000000000000000000000000000000000000000006ba66909eaf365ed00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000035696b86aba0e633fae00852d0022899b769cbd8f6eaf3059246669342f600006b5bcc2b578c10c5a89464179da2999eb71e0a9d554fb33eb70a30c4e4df71f5000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000084040000a14dc6f5db4bd72d016f6f66040bb86a00210000b4f95365e8fb345e357c35bcc4e58cc99015759ce5fee19701b51096f0494baf
2017-04-10 20:52:45 INFO: TransactionImpl.checkSignature: [SIGN] Verifying HEX:03149d3e5a060300964be53db0cc61dd465fa765b03651c1bb06c7ce6b738be739ee1f143ea1910f00000000000000000000000000000000000000000000000000000000000000006ba66909eaf365ed00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000084040000a14dc6f5db4bd72d016f6f66040bb86a00210000b4f95365e8fb345e357c35bcc4e58cc99015759ce5fee19701b51096f0494baf
Zero'ed HEX: 03149d3e5a060300964be53db0cc61dd465fa765b03651c1bb06c7ce6b738be739ee1f143ea1910f00000000000000000000000000000000000000000000000000000000000000006ba66909eaf365ed00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000084040000a14dc6f5db4bd72d016f6f66040bb86a00210000b4f95365e8fb345e357c35bcc4e58cc99015759ce5fee19701b51096f0494baf
Json Trans.: {"senderPublicKey":"964be53db0cc61dd465fa765b03651c1bb06c7ce6b738be739ee1f143ea1910f","attachment":{"version.PiggybackedProofOfBountyAnnouncement":1,"id":"30038704989302639","hash_announced":"b4f95365e8fb345e357c35bcc4e58cc99015759ce5fee19701b51096f0494baf"},"subtype":4,"amountNQT":0,"signature":"35696b86aba0e633fae00852d0022899b769cbd8f6eaf3059246669342f600006b5bcc2b578c10c5a89464179da2999eb71e0a9d554fb33eb70a30c4e4df71f5","feeNQT":0,"ecBlockHeight":1156,"type":3,"deadline":3,"version":1,"timestamp":106577565,"ecBlockId":"3303192259792883105"}
VERIFY RESULT: true
Trans. IDNR: 9573744148325208918
2017-04-10 20:52:45 INFO: TransactionProcessorImpl.broadcast: Accepted new transaction 9573744148325208918
2017-04-10 20:52:58 INFO: TransactionImpl.: [SIGN] Signing HEX: 0312ab3e5a060300964be53db0cc61dd465fa765b03651c1bb06c7ce6b738be739ee1f143ea1910f00000000000000000000000000000000000000000000000000000000000000006ba66909eaf365ed00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000084040000a14dc6f5db4bd72d016f6f66040bb86a000000000000000000a6032307000000000000000000000000867e888a050c7859
Json Trans.: {"senderPublicKey":"964be53db0cc61dd465fa765b03651c1bb06c7ce6b738be739ee1f143ea1910f","attachment":{"version.PiggybackedProofOfWork":1,"id":"30038704989302639","multiplicator":"a6032307000000000000000000000000867e888a050c7859"},"subtype":2,"amountNQT":0,"signature":"8e5f0ec7d5e9d69d8ff46774e3031c1c85e52d2fbcdcf360e24302a7ceae1a0a8b377ed1675380ee930da07c7aa23d04645259d50d6e67ad302492748d6e6f08","feeNQT":0,"ecBlockHeight":1156,"type":3,"deadline":3,"version":1,"timestamp":106577579,"ecBlockId":"3303192259792883105"}
Trans. IDNR: 1416522640852673254
2017-04-10 20:52:58 INFO: TransactionProcessorImpl.broadcast: [SIGN] Broadcasting TX: 0312ab3e5a060300964be53db0cc61dd465fa765b03651c1bb06c7ce6b738be739ee1f143ea1910f00000000000000000000000000000000000000000000000000000000000000006ba66909eaf365ed0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000008e5f0ec7d5e9d69d8ff46774e3031c1c85e52d2fbcdcf360e24302a7ceae1a0a8b377ed1675380ee930da07c7aa23d04645259d50d6e67ad302492748d6e6f08000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000084040000a14dc6f5db4bd72d016f6f66040bb86a000000000000000000a6032307000000000000000000000000867e888a050c7859
2017-04-10 20:52:58 INFO: TransactionProcessorImpl.broadcast: Transaction 1416522640852673254 is relayed to SN.
2017-04-10 20:55:31 SEVERE: TransactionProcessorImpl.lambda$new$175: Error removing unconfirmed transactions
java.lang.RuntimeException: java.lang.RuntimeException: nxt.NxtException$NotValidException: Transaction bytes too long, 33 extra bytes, TX type = 3:4
   at nxt.db.DbIterator.next(DbIterator.java:87)
   at nxt.TransactionProcessorImpl.lambda$new$175(TransactionProcessorImpl.java:207)
   at nxt.TransactionProcessorImpl$$Lambda$26/7313060.run(Unknown Source)
   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)
Caused by: java.lang.RuntimeException: nxt.NxtException$NotValidException: Transaction bytes too long, 33 extra bytes, TX type = 3:4
   at nxt.UnconfirmedTransaction.(UnconfirmedTransaction.java:67)
   at nxt.TransactionProcessorImpl$2.load(TransactionProcessorImpl.java:108)
   at nxt.TransactionProcessorImpl$2.load(TransactionProcessorImpl.java:98)
   at nxt.db.EntityDbTable.lambda$getManyBy$4(EntityDbTable.java:294)
   at nxt.db.EntityDbTable$$Lambda$65/16868041.get(Unknown Source)
   at nxt.db.DbIterator.next(DbIterator.java:82)
   ... 9 more
Caused by: nxt.NxtException$NotValidException: Transaction bytes too long, 33 extra bytes, TX type = 3:4
   at nxt.TransactionImpl.newTransactionBuilder(TransactionImpl.java:279)
   at nxt.TransactionImpl.newTransactionBuilder(TransactionImpl.java:291)
   at nxt.UnconfirmedTransaction.(UnconfirmedTransaction.java:60)
   ... 14 more
2017-04-10 20:55:51 SEVERE: TransactionProcessorImpl.lambda$new$175: Error removing unconfirmed transactions
java.lang.RuntimeException: java.lang.RuntimeException: nxt.NxtException$NotValidException: Transaction bytes too long, 33 extra bytes, TX type = 3:4
   at nxt.db.DbIterator.next(DbIterator.java:87)
   at nxt.TransactionProcessorImpl.lambda$new$175(TransactionProcessorImpl.java:207)
   at nxt.TransactionProcessorImpl$$Lambda$26/7313060.run(Unknown Source)
   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)
Caused by: java.lang.RuntimeException: nxt.NxtException$NotValidException: Transaction bytes too long, 33 extra bytes, TX type = 3:4
   at nxt.UnconfirmedTransaction.(UnconfirmedTransaction.java:67)
   at nxt.TransactionProcessorImpl$2.load(TransactionProcessorImpl.java:108)
   at nxt.TransactionProcessorImpl$2.load(TransactionProcessorImpl.java:98)
   at nxt.db.EntityDbTable.lambda$getManyBy$4(EntityDbTable.java:294)
   at nxt.db.EntityDbTable$$Lambda$65/16868041.get(Unknown Source)
   at nxt.db.DbIterator.next(DbIterator.java:82)
   ... 9 more
Caused by: nxt.NxtException$NotValidException: Transaction bytes too long, 33 extra bytes, TX type = 3:4
   at nxt.TransactionImpl.newTransactionBuilder(TransactionImpl.java:279)
   at nxt.TransactionImpl.newTransactionBuilder(TransactionImpl.java:291)
   at nxt.UnconfirmedTransaction.(UnconfirmedTransaction.java:60)
   ... 14 more
2017-04-10 20:56:11 SEVERE: TransactionProcessorImpl.lambda$new$175: Error removing unconfirmed transactions
java.lang.RuntimeException: java.lang.RuntimeException: nxt.NxtException$NotValidException: Transaction bytes too long, 33 extra bytes, TX type = 3:4
   at nxt.db.DbIterator.next(DbIterator.java:87)
   at nxt.TransactionProcessorImpl.lambda$new$175(TransactionProcessorImpl.java:207)
   at nxt.TransactionProcessorImpl$$Lambda$26/7313060.run(Unknown Source)
   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)
Caused by: java.lang.RuntimeException: nxt.NxtException$NotValidException: Transaction bytes too long, 33 extra bytes, TX type = 3:4
   at nxt.UnconfirmedTransaction.(UnconfirmedTransaction.java:67)
   at nxt.TransactionProcessorImpl$2.load(TransactionProcessorImpl.java:108)
   at nxt.TransactionProcessorImpl$2.load(TransactionProcessorImpl.java:98)
   at nxt.db.EntityDbTable.lambda$getManyBy$4(EntityDbTable.java:294)
   at nxt.db.EntityDbTable$$Lambda$65/16868041.get(Unknown Source)
   at nxt.db.DbIterator.next(DbIterator.java:82)
   ... 9 more
Caused by: nxt.NxtException$NotValidException: Transaction bytes too long, 33 extra bytes, TX type = 3:4
   at nxt.TransactionImpl.newTransactionBuilder(TransactionImpl.java:279)
   at nxt.TransactionImpl.newTransactionBuilder(TransactionImpl.java:291)
   at nxt.UnconfirmedTransaction.(UnconfirmedTransaction.java:60)
   ... 14 more
2017-04-10 20:56:31 SEVERE: TransactionProcessorImpl.lambda$new$175: Error removing unconfirmed transactions
java.lang.RuntimeException: java.lang.RuntimeException: nxt.NxtException$NotValidException: Transaction bytes too long, 33 extra bytes, TX type = 3:4
   at nxt.db.DbIterator.next(DbIterator.java:87)
   at nxt.TransactionProcessorImpl.lambda$new$175(TransactionProcessorImpl.java:207)
   at nxt.TransactionProcessorImpl$$Lambda$26/7313060.run(Unknown Source)
   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)
Caused by: java.lang.RuntimeException: nxt.NxtException$NotValidException: Transaction bytes too long, 33 extra bytes, TX type = 3:4
   at nxt.UnconfirmedTransaction.(UnconfirmedTransaction.java:67)
   at nxt.TransactionProcessorImpl$2.load(TransactionProcessorImpl.java:108)
   at nxt.TransactionProcessorImpl$2.load(TransactionProcessorImpl.java:98)
   at nxt.db.EntityDbTable.lambda$getManyBy$4(EntityDbTable.java:294)
   at nxt.db.EntityDbTable$$Lambda$65/16868041.get(Unknown Source)
   at nxt.db.DbIterator.next(DbIterator.java:82)
   ... 9 more
Caused by: nxt.NxtException$NotValidException: Transaction bytes too long, 33 extra bytes, TX type = 3:4
   at nxt.TransactionImpl.newTransactionBuilder(TransactionImpl.java:279)
   at nxt.TransactionImpl.newTransactionBuilder(TransactionImpl.java:291)
   at nxt.UnconfirmedTransaction.(UnconfirmedTransaction.java:60)
   ... 14 more
2017-04-10 20:56:51 SEVERE: TransactionProcessorImpl.lambda$new$175: Error removing unconfirmed transactions
java.lang.RuntimeException: java.lang.RuntimeException: nxt.NxtException$NotValidException: Transaction bytes too long, 33 extra bytes, TX type = 3:4
   at nxt.db.DbIterator.next(DbIterator.java:87)
   at nxt.TransactionProcessorImpl.lambda$new$175(TransactionProcessorImpl.java:207)
   at nxt.TransactionProcessorImpl$$Lambda$26/7313060.run(Unknown Source)
   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)
Caused by: java.lang.RuntimeException: nxt.NxtException$NotValidException: Transaction bytes too long, 33 extra bytes, TX type = 3:4
   at nxt.UnconfirmedTransaction.(UnconfirmedTransaction.java:67)
   at nxt.TransactionProcessorImpl$2.load(TransactionProcessorImpl.java:108)
   at nxt.TransactionProcessorImpl$2.load(TransactionProcessorImpl.java:98)
   at nxt.db.EntityDbTable.lambda$getManyBy$4(EntityDbTable.java:294)
   at nxt.db.EntityDbTable$$Lambda$65/16868041.get(Unknown Source)
   at nxt.db.DbIterator.next(DbIterator.java:82)
   ... 9 more
Caused by: nxt.NxtException$NotValidException: Transaction bytes too long, 33 extra bytes, TX type = 3:4
   at nxt.TransactionImpl.newTransactionBuilder(TransactionImpl.java:279)
   at nxt.TransactionImpl.newTransactionBuilder(TransactionImpl.java:291)
   at nxt.UnconfirmedTransaction.(UnconfirmedTransaction.java:60)
   ... 14 more
2017-04-10 20:57:11 SEVERE: TransactionProcessorImpl.lambda$new$175: Error removing unconfirmed transactions
java.lang.RuntimeException: java.lang.RuntimeException: nxt.NxtException$NotValidException: Transaction bytes too long, 33 extra bytes, TX type = 3:4
   at nxt.db.DbIterator.next(DbIterator.java:87)
   at nxt.TransactionProcessorImpl.lambda$new$175(TransactionProcessorImpl.java:207)
   at nxt.TransactionProcessorImpl$$Lambda$26/7313060.run(Unknown Source)
   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)
Caused by: java.lang.RuntimeException: nxt.NxtException$NotValidException: Transaction bytes too long, 33 extra bytes, TX type = 3:4
   at nxt.UnconfirmedTransaction.(UnconfirmedTransaction.java:67)
   at nxt.TransactionProcessorImpl$2.load(TransactionProcessorImpl.java:108)
   at nxt.TransactionProcessorImpl$2.load(TransactionProcessorImpl.java:98)
   at nxt.db.EntityDbTable.lambda$getManyBy$4(EntityDbTable.java:294)
   at nxt.db.EntityDbTable$$Lambda$65/16868041.get(Unknown Source)
   at nxt.db.DbIterator.next(DbIterator.java:82)
   ... 9 more
Caused by: nxt.NxtException$NotValidException: Transaction bytes too long, 33 extra bytes, TX type = 3:4
   at nxt.TransactionImpl.newTransactionBuilder(TransactionImpl.java:279)
   at nxt.TransactionImpl.newTransactionBuilder(TransactionImpl.java:291)
   at nxt.UnconfirmedTransaction.(UnconfirmedTransaction.java:60)
   ... 14 more
2017-04-10 20:57:31 SEVERE: TransactionProcessorImpl.lambda$new$175: Error removing unconfirmed transactions
java.lang.RuntimeException: java.lang.RuntimeException: nxt.NxtException$NotValidException: Transaction bytes too long, 33 extra bytes, TX type = 3:4
   at nxt.db.DbIterator.next(DbIterator.java:87)
   at nxt.TransactionProcessorImpl.lambda$new$175(TransactionProcessorImpl.java:207)
   at nxt.TransactionProcessorImpl$$Lambda$26/7313060.run(Unknown Source)
   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)
Caused by: java.lang.RuntimeException: nxt.NxtException$NotValidException: Transaction bytes too long, 33 extra bytes, TX type = 3:4
   at nxt.UnconfirmedTransaction.(UnconfirmedTransaction.java:67)
   at nxt.TransactionProcessorImpl$2.load(TransactionProcessorImpl.java:108)
   at nxt.TransactionProcessorImpl$2.load(TransactionProcessorImpl.java:98)
   at nxt.db.EntityDbTable.lambda$getManyBy$4(EntityDbTable.java:294)
   at nxt.db.EntityDbTable$$Lambda$65/16868041.get(Unknown Source)
   at nxt.db.DbIterator.next(DbIterator.java:82)
   ... 9 more
Caused by: nxt.NxtException$NotValidException: Transaction bytes too long, 33 extra bytes, TX type = 3:4
   at nxt.TransactionImpl.newTransactionBuilder(TransactionImpl.java:279)
   at nxt.TransactionImpl.newTransactionBuilder(TransactionImpl.java:291)
   at nxt.UnconfirmedTransaction.(UnconfirmedTransaction.java:60)
   ... 14 more
2017-04-10 20:57:51 SEVERE: TransactionProcessorImpl.lambda$new$175: Error removing unconfirmed transactions
java.lang.RuntimeException: java.lang.RuntimeException: nxt.NxtException$NotValidException: Transaction bytes too long, 33 extra bytes, TX type = 3:4
   at nxt.db.DbIterator.next(DbIterator.java:87)
   at nxt.TransactionProcessorImpl.lambda$new$175(TransactionProcessorImpl.java:207)
   at nxt.TransactionProcessorImpl$$Lambda$26/7313060.run(Unknown Source)
   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)
Caused by: java.lang.RuntimeException: nxt.NxtException$NotValidException: Transaction bytes too long, 33 extra bytes, TX type = 3:4
   at nxt.UnconfirmedTransaction.(UnconfirmedTransaction.java:67)
   at nxt.TransactionProcessorImpl$2.load(TransactionProcessorImpl.java:108)
   at nxt.TransactionProcessorImpl$2.load(TransactionProcessorImpl.java:98)
   at nxt.db.EntityDbTable.lambda$getManyBy$4(EntityDbTable.java:294)
   at nxt.db.EntityDbTable$$Lambda$65/16868041.get(Unknown Source)
   at nxt.db.DbIterator.next(DbIterator.java:82)
   ... 9 more
Caused by: nxt.NxtException$NotValidException: Transaction bytes too long, 33 extra bytes, TX type = 3:4
   at nxt.TransactionImpl.newTransactionBuilder(TransactionImpl.java:279)
   at nxt.TransactionImpl.newTransactionBuilder(TransactionImpl.java:291)
   at nxt.UnconfirmedTransaction.(UnconfirmedTransaction.java:60)
   ... 14 more
2017-04-10 20:58:11 SEVERE: TransactionProcessorImpl.lambda$new$175: Error removing unconfirmed transactions
java.lang.RuntimeException: java.lang.RuntimeException: nxt.NxtException$NotValidException: Transaction bytes too long, 33 extra bytes, TX type = 3:4
   at nxt.db.DbIterator.next(DbIterator.java:87)
   at nxt.TransactionProcessorImpl.lambda$new$175(TransactionProcessorImpl.java:207)
   at nxt.TransactionProcessorImpl$$Lambda$26/7313060.run(Unknown Source)
   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)
Caused by: java.lang.RuntimeException: nxt.NxtException$NotValidException: Transaction bytes too long, 33 extra bytes, TX type = 3:4
   at nxt.UnconfirmedTransaction.(UnconfirmedTransaction.java:67)
   at nxt.TransactionProcessorImpl$2.load(TransactionProcessorImpl.java:108)
   at nxt.TransactionProcessorImpl$2.load(TransactionProcessorImpl.java:98)
   at nxt.db.EntityDbTable.lambda$getManyBy$4(EntityDbTable.java:294)
   at nxt.db.EntityDbTable$$Lambda$65/16868041.get(Unknown Source)
   at nxt.db.DbIterator.next(DbIterator.java:82)
   ... 9 more
Caused by: nxt.NxtException$NotValidException: Transaction bytes too long, 33 extra bytes, TX type = 3:4
   at nxt.TransactionImpl.newTransactionBuilder(TransactionImpl.java:279)
   at nxt.TransactionImpl.newTransactionBuilder(TransactionImpl.java:291)
   at nxt.UnconfirmedTransaction.(UnconfirmedTransaction.java:60)
   ... 14 more
2017-04-10 20:58:31 SEVERE: TransactionProcessorImpl.lambda$new$175: Error removing unconfirmed transactions
java.lang.RuntimeException: java.lang.RuntimeException: nxt.NxtException$NotValidException: Transaction bytes too long, 33 extra bytes, TX type = 3:4
   at nxt.db.DbIterator.next(DbIterator.java:87)
   at nxt.TransactionProcessorImpl.lambda$new$175(TransactionProcessorImpl.java:207)
   at nxt.TransactionProcessorImpl$$Lambda$26/7313060.run(Unknown Source)
   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)
Caused by: java.lang.RuntimeException: nxt.NxtException$NotValidException: Transaction bytes too long, 33 extra bytes, TX type = 3:4
   at nxt.UnconfirmedTransaction.(UnconfirmedTransaction.java:67)
   at nxt.TransactionProcessorImpl$2.load(TransactionProcessorImpl.java:108)
   at nxt.TransactionProcessorImpl$2.load(TransactionProcessorImpl.java:98)
   at nxt.db.EntityDbTable.lambda$getManyBy$4(EntityDbTable.java:294)
   at nxt.db.EntityDbTable$$Lambda$65/16868041.get(Unknown Source)
   at nxt.db.DbIterator.next(DbIterator.java:82)
   ... 9 more
Caused by: nxt.NxtException$NotValidException: Transaction bytes too long, 33 extra bytes, TX type = 3:4
   at nxt.TransactionImpl.newTransactionBuilder(TransactionImpl.java:279)
   at nxt.TransactionImpl.newTransactionBuilder(TransactionImpl.java:291)
   at nxt.UnconfirmedTransaction.(UnconfirmedTransaction.java:60)
   ... 14 more
2017-04-10 20:58:51 SEVERE: TransactionProcessorImpl.lambda$new$175: Error removing unconfirmed transactions
java.lang.RuntimeException: java.lang.RuntimeException: nxt.NxtException$NotValidException: Transaction bytes too long, 33 extra bytes, TX type = 3:4
   at nxt.db.DbIterator.next(DbIterator.java:87)
   at nxt.TransactionProcessorImpl.lambda$new$175(TransactionProcessorImpl.java:207)
   at nxt.TransactionProcessorImpl$$Lambda$26/7313060.run(Unknown Source)
   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)
Caused by: java.lang.RuntimeException: nxt.NxtException$NotValidException: Transaction bytes too long, 33 extra bytes, TX type = 3:4
   at nxt.UnconfirmedTransaction.(UnconfirmedTransaction.java:67)
   at nxt.TransactionProcessorImpl$2.load(TransactionProcessorImpl.java:108)
   at nxt.TransactionProcessorImpl$2.load(TransactionProcessorImpl.java:98)
   at nxt.db.EntityDbTable.lambda$getManyBy$4(EntityDbTable.java:294)
   at nxt.db.EntityDbTable$$Lambda$65/16868041.get(Unknown Source)
   at nxt.db.DbIterator.next(DbIterator.java:82)
   ... 9 more
Caused by: nxt.NxtException$NotValidException: Transaction bytes too long, 33 extra bytes, TX type = 3:4
   at nxt.TransactionImpl.newTransactionBuilder(TransactionImpl.java:279)
   at nxt.TransactionImpl.newTransactionBuilder(TransactionImpl.java:291)
   at nxt.UnconfirmedTransaction.(UnconfirmedTransaction.java:60)
   ... 14 more
2017-04-10 20:59:11 SEVERE: TransactionProcessorImpl.lambda$new$175: Error removing unconfirmed transactions
java.lang.RuntimeException: java.lang.RuntimeException: nxt.NxtException$NotValidException: Transaction bytes too long, 33 extra bytes, TX type = 3:4
   at nxt.db.DbIterator.next(DbIterator.java:87)
   at nxt.TransactionProcessorImpl.lambda$new$175(TransactionProcessorImpl.java:207)
   at nxt.TransactionProcessorImpl$$Lambda$26/7313060.run(Unknown Source)
   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)
Caused by: java.lang.RuntimeException: nxt.NxtException$NotValidException: Transaction bytes too long, 33 extra bytes, TX type = 3:4
   at nxt.UnconfirmedTransaction.(UnconfirmedTransaction.java:67)
   at nxt.TransactionProcessorImpl$2.load(TransactionProcessorImpl.java:108)
   at nxt.TransactionProcessorImpl$2.load(TransactionProcessorImpl.java:98)
   at nxt.db.EntityDbTable.lambda$getManyBy$4(EntityDbTable.java:294)
   at nxt.db.EntityDbTable$$Lambda$65/16868041.get(Unknown Source)
   at nxt.db.DbIterator.next(DbIterator.java:82)
   ... 9 more
Caused by: nxt.NxtException$NotValidException: Transaction bytes too long, 33 extra bytes, TX type = 3:4
   at nxt.TransactionImpl.newTransactionBuilder(TransactionImpl.java:279)
   at nxt.TransactionImpl.newTransactionBuilder(TransactionImpl.java:291)
   at nxt.UnconfirmedTransaction.(UnconfirmedTransaction.java:60)
   ... 14 more
2017-04-10 20:59:31 SEVERE: TransactionProcessorImpl.lambda$new$175: Error removing unconfirmed transactions
java.lang.RuntimeException: java.lang.RuntimeException: nxt.NxtException$NotValidException: Transaction bytes too long, 33 extra bytes, TX type = 3:4
   at nxt.db.DbIterator.next(DbIterator.java:87)
   at nxt.TransactionProcessorImpl.lambda$new$175(TransactionProcessorImpl.java:207)
   at nxt.TransactionProcessorImpl$$Lambda$26/7313060.run(Unknown Source)
   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)
Caused by: java.lang.RuntimeException: nxt.NxtException$NotValidException: Transaction bytes too long, 33 extra bytes, TX type = 3:4
   at nxt.UnconfirmedTransaction.(UnconfirmedTransaction.java:67)
   at nxt.TransactionProcessorImpl$2.load(TransactionProcessorImpl.java:108)
   at nxt.TransactionProcessorImpl$2.load(TransactionProcessorImpl.java:98)
   at nxt.db.EntityDbTable.lambda$getManyBy$4(EntityDbTable.java:294)
   at nxt.db.EntityDbTable$$Lambda$65/16868041.get(Unknown Source)
   at nxt.db.DbIterator.next(DbIterator.java:82)
   ... 9 more
Caused by: nxt.NxtException$NotValidException: Transaction bytes too long, 33 extra bytes, TX type = 3:4
   at nxt.TransactionImpl.newTransactionBuilder(TransactionImpl.java:279)
   at nxt.TransactionImpl.newTransactionBuilder(TransactionImpl.java:291)
   at nxt.UnconfirmedTransaction.(UnconfirmedTransaction.java:60)
   ... 14 more
2017-04-10 20:59:51 SEVERE: TransactionProcessorImpl.lambda$new$175: Error removing unconfirmed transactions
java.lang.RuntimeException: java.lang.RuntimeException: nxt.NxtException$NotValidException: Transaction bytes too long, 33 extra bytes, TX type = 3:4
   at nxt.db.DbIterator.next(DbIterator.java:87)
   at nxt.TransactionProcessorImpl.lambda$new$175(TransactionProcessorImpl.java:207)
   at nxt.TransactionProcessorImpl$$Lambda$26/7313060.run(Unknown Source)
   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)
Caused by: java.lang.RuntimeException: nxt.NxtException$NotValidException: Transaction bytes too long, 33 extra bytes, TX type = 3:4
   at nxt.UnconfirmedTransaction.(UnconfirmedTransaction.java:67)
   at nxt.TransactionProcessorImpl$2.load(TransactionProcessorImpl.java:108)
   at nxt.TransactionProcessorImpl$2.load(TransactionProcessorImpl.java:98)
   at nxt.db.EntityDbTable.lambda$getManyBy$4(EntityDbTable.java:294)
   at nxt.db.EntityDbTable$$Lambda$65/16868041.get(Unknown Source)
   at nxt.db.DbIterator.next(DbIterator.java:82)
   ... 9 more
Caused by: nxt.NxtException$NotValidException: Transaction bytes too long, 33 extra bytes, TX type = 3:4
   at nxt.TransactionImpl.newTransactionBuilder(TransactionImpl.java:279)
   at nxt.TransactionImpl.newTransactionBuilder(TransactionImpl.java:291)
   at nxt.UnconfirmedTransaction.(UnconfirmedTransaction.java:60)
   ... 14 more

ghoom2

sr. member

Activity: 548

Merit: 265

My old account was "Ghoom" (hacked) u=199247

Quote from: Evil-Knievel on April 10, 2017, 03:32:19 PM

Quote from: Evil-Knievel on April 10, 2017, 02:52:11 PM

Quote from: ghoom2 on April 10, 2017, 11:58:54 AM

Stopped on Block 1068 Sad

Elastic 1.0.5

This bug is becoming a pain in the ass ;-)
Fixing ... aaaand another night goes into the shitter.

The bug is fixed! Now once for all.
Clients should sync fine now even without update.

BUT: You should git-pull the latest version so you don't get blacklisted by others. No need to delete elastic_test_db!

Perfect !

Evil-Knievel

legendary

Activity: 1260

Merit: 1168

Account with passphrase "test" has 20k+ Test-XEL in it which are not needed anymore. Take it if you want ;-)

Evil-Knievel

legendary

Activity: 1260

Merit: 1168

Quote from: Evil-Knievel on April 10, 2017, 02:52:11 PM

Quote from: ghoom2 on April 10, 2017, 11:58:54 AM

Stopped on Block 1068 Sad

Elastic 1.0.5

This bug is becoming a pain in the ass ;-)
Fixing ... aaaand another night goes into the shitter.

The bug is fixed! Now once for all.
Clients should sync fine now even without update.

BUT: You should git-pull the latest version so you don't get blacklisted by others. No need to delete elastic_test_db!

logictense

hero member

Activity: 2147

Merit: 518

Quote from: Evil-Knievel on April 10, 2017, 09:26:46 AM

Quote from: devking on April 10, 2017, 05:54:46 AM

@EK,

I have updated my node with from 1.0.4, latest version 1.0.5, well known test peers returning errors. My peer blacklisted. Can you please unblock.

azonaws.com

Getting errors

2017-04-10 10:48:52 FINE: PeerImpl.send: Peer 52.28.123.208 version null returned error: {"cause":"Old version: 1.0.4","error":"Your peer is blacklisted"}, request was: {"protocol":1,"apiPort":6876,"application":"Elastic","apiServerIdleTimeout":30000,"requestType":"getInfo","blockchainState":1,"services":"20","version":"1.0.5","platform":"Linux amd64","disabledAPIs":"","shareAddress":true}, disconnecting

2017-04-10 10:48:52 FINE: PeerImpl.send: Peer 52.57.31.137 version null returned error: {"cause":"Old version: 1.0.4","error":"Your peer is blacklisted"}, request was: {"protocol":1,"apiPort":6876,"application":"Elastic","apiServerIdleTimeout":30000,"requestType":"getInfo","blockchainState":1,"services":"20","version":"1.0.5","platform":"Linux amd64","disabledAPIs":"","shareAddress":true}, disconnecting

Are you sure?
It might be possible that you didn't upgrade because the "git pull" failed due to some conflict. Have you made a "git stash" before?

Nope I dont. It seems like my machine is acting up, throwing weird requests right into my face. My shoulders are huge and I can handle that load, dont worry about me. Today or tomorrow I will get in contact with u on the matter that we were discussing when ur mom arrived and spoiled our party. Im getting a bazillion of other errors, too but will not reveal this as its beyond the scope of my post.

Evil-Knievel

legendary

Activity: 1260

Merit: 1168

Quote from: ghoom2 on April 10, 2017, 11:58:54 AM

Stopped on Block 1068 Sad

Elastic 1.0.5

This bug is becoming a pain in the ass ;-)
Fixing ... aaaand another night goes into the shitter.

unvoid

hero member

Activity: 535

Merit: 500

Quote from: ghoom2 on April 10, 2017, 11:58:54 AM

Stopped on Block 1068 Sad

Elastic 1.0.5

Same here. Second node wont even connect to the peers but I think it's more like this node fault or hard ban.

https://talk.elasticexplorer.org/t/1-0-5-stuck-at-block-1068/92

ghoom2

sr. member

Activity: 548

Merit: 265

My old account was "Ghoom" (hacked) u=199247

Stopped on Block 1068 Sad

Elastic 1.0.5

Topic: [ANN][XEL] Elastic Project - The Decentralized Supercomputer - page 96. (Read 450522 times)