Bitcoin Forum
October 17, 2019, 06:30:55 AM *
News: Latest Bitcoin Core release: 0.18.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 [250] 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 ... 346 »
  Print  
Author Topic: [ANN][XEL] Elastic Project - The Decentralized Supercomputer  (Read 449747 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
April 10, 2017, 03:51:15 PM
 #4981

@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?

I had same error yesterday. In my case I was banned with info that I have version 1.0.3 (of course after git pull and compile). I didn't want to play with it so I deleted all source and cloned fresh from github. Worked like a charm. Just be sure you backup your nxt.properties before that.

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

Posts: 1571293855

View Profile Personal Message (Offline)

Ignore
1571293855
Reply with quote  #2

1571293855
Report to moderator
1571293855
Hero Member
*
Offline Offline

Posts: 1571293855

View Profile Personal Message (Offline)

Ignore
1571293855
Reply with quote  #2

1571293855
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1571293855
Hero Member
*
Offline Offline

Posts: 1571293855

View Profile Personal Message (Offline)

Ignore
1571293855
Reply with quote  #2

1571293855
Report to moderator
ghoom2
Sr. Member
****
Offline Offline

Activity: 550
Merit: 265

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


View Profile
April 10, 2017, 04:58:54 PM
 #4982

Stopped on Block 1068 Sad

Elastic 1.0.5

█████████████ ⚡ BITCOIN 2 ⚡ ███████c█████████████████
█████████████ ⚡ Join the discussion thread ⚡ █████████████
👀 Private  ⚡ Fast  ¢ Low fees 🔴 Scalable 💡 Economical  ❂ Decentralized
unvoid
Hero Member
*****
Offline Offline

Activity: 535
Merit: 500



View Profile
April 10, 2017, 06:17:54 PM
Last edit: April 10, 2017, 07:16:43 PM by unvoid
 #4983

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

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

Activity: 1274
Merit: 1160



View Profile
April 10, 2017, 07:52:11 PM
 #4984

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.
logictense
Hero Member
*****
Offline Offline

Activity: 1302
Merit: 511


View Profile WWW
April 10, 2017, 08:00:09 PM
 #4985

@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
*
Offline Offline

Activity: 1274
Merit: 1160



View Profile
April 10, 2017, 08:32:19 PM
 #4986

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!
Evil-Knievel
Legendary
*
Offline Offline

Activity: 1274
Merit: 1160



View Profile
April 10, 2017, 08:40:44 PM
 #4987

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

Activity: 550
Merit: 265

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


View Profile
April 10, 2017, 09:41:39 PM
 #4988

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 !

█████████████ ⚡ BITCOIN 2 ⚡ ███████c█████████████████
█████████████ ⚡ Join the discussion thread ⚡ █████████████
👀 Private  ⚡ Fast  ¢ Low fees 🔴 Scalable 💡 Economical  ❂ Decentralized
coralreefer
Sr. Member
****
Offline Offline

Activity: 465
Merit: 260


View Profile
April 11, 2017, 01:07:39 AM
 #4989

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.<init>: [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.<init>: [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.<init>: [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.<init>: [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.<init>(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.<init>(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.<init>(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.<init>(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.<init>(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.<init>(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.<init>(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.<init>(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.<init>(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.<init>(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.<init>(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.<init>(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.<init>(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.<init>(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.<init>(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.<init>(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.<init>(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.<init>(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.<init>(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.<init>(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.<init>(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.<init>(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.<init>(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.<init>(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.<init>(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.<init>(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.<init>(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.<init>(UnconfirmedTransaction.java:60)
        ... 14 more
Evil-Knievel
Legendary
*
Offline Offline

Activity: 1274
Merit: 1160



View Profile
April 11, 2017, 04:02:41 AM
 #4990

@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.
by rallier
Legendary
*
Offline Offline

Activity: 1414
Merit: 1278


App Security Engineer, Cryptocurrency Enthusiast


View Profile WWW
April 11, 2017, 10:55:49 AM
 #4991

@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.

To hire a Security Engineer, contact me.
Evil-Knievel
Legendary
*
Offline Offline

Activity: 1274
Merit: 1160



View Profile
April 11, 2017, 05:39:27 PM
 #4992

Just thinking out loud: do we really need the bounty announcements in the new SN scheme?
unvoid
Hero Member
*****
Offline Offline

Activity: 535
Merit: 500



View Profile
April 11, 2017, 06:30:34 PM
 #4993

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.

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

Activity: 535
Merit: 500



View Profile
April 11, 2017, 06:32:08 PM
 #4994

@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

BTC: 1CMgHWx4wkAaAy2FfeCyPdedUExmhGhfi5
XEL: XEL-HCM8-KB6E-YFLK-8BWMF
MostlyGhostly
Full Member
***
Offline Offline

Activity: 268
Merit: 100


View Profile
April 11, 2017, 06:38:01 PM
 #4995

@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
*****
Offline Offline

Activity: 535
Merit: 500



View Profile
April 11, 2017, 07:22:59 PM
 #4996

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).

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

Activity: 535
Merit: 500



View Profile
April 11, 2017, 07:27:06 PM
 #4997

Forum stats from last 24h by google analytics.


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

Activity: 535
Merit: 500



View Profile
April 11, 2017, 07:32:07 PM
 #4998

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


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

Activity: 465
Merit: 260


View Profile
April 11, 2017, 08:04:18 PM
 #4999

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.

Evil-Knievel
Legendary
*
Offline Offline

Activity: 1274
Merit: 1160



View Profile
April 11, 2017, 08:38:08 PM
 #5000

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.
Pages: « 1 ... 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 [250] 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 ... 346 »
  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!