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

unvoid

hero member

Activity: 535

Merit: 500

Quote from: skya on September 01, 2016, 02:43:14 AM

hey man
I donated, when are my XEL going to be activated?
Thx.

As soon as testnet prove that everything working fine. Mainnet not sooner than two months I think. But you can play now with XEL, just download testnet client https://github.com/OrdinaryDude/elastic-reference-client watch this video for instructions how to run it https://player.vimeo.com/video/178616474?quality=1080p and paste your address here to receive some XEL for testing and fun.

unvoid

hero member

Activity: 535

Merit: 500

Great @EK! I was reading the code yesterday trying to find what's wrong but couldn't conclude what's exactly wrong with it. Awesome we have you. I'm up and runnig with new version already. As soon I'll get test-XEL I'll try to crush it again

. Also I'll create a pull request for elastic-miner later this day after my work. With port fix and compile/run scripts like in XEL.

( @ImI Request XEL-7UTR-VYZY-ZUZZ-DTJJ5 , same amount )

@EK does any node up right now? I've 0 connections.

EDIT: Ah, it's ok. I copied old nxt.properties but forgot that testnetPeers changed.

skya

member

Activity: 119

Merit: 100

hey man
I donated, when are my XEL going to be activated?
Thx.

Evil-Knievel

legendary

Activity: 1260

Merit: 1168

BUG IS FIXED!

;-) However we need to reset the testnet.

- Update your code (git pull)
- Remove your old blockchain (rm -rf nxt_test_db). (!!!!!! IMPORTANT)
- and reconnect.

Also, the public testnet node has changed:
http://ec2-52-28-123-208.eu-central-1.compute.amazonaws.com:6876/index.html

Old clients will no more be able to connect, as the new Elastic version is not 0.2.0

Thanks again for crashing.

The Bug was the following:

When a work cancellation was submitted, it checked in the transaction validation routine if the work was still pending.

Code:

if (WorkLogicManager.getInstance().isStillPending(attachment.getWorkId(), transaction.getSenderId()) == false) {
throw new NxtException.NotValidException("Cannot cancel already cancelled or finished work");
}

Unfortunately it also checked if the work cancellation was sent by the original author. This was correct earlier before the protocol revamp,
but now we have a work cancellation request (the original author must send this if he wants to cancel before the regular deadline) and the actual work cancellation is created by the one who mines the block. So whenever someone else mins a block which cancels someone else work, it all crashes.

This is by the way how a bug report for a bug bounty must look like! (It must have a good description) Wink

Nonetheless, Lannister I would say you give away 1 BTC (maybe split it up?) to those who found the bug, that means to the one who created the work and the one who mined the block. Would you be OK with that?

I would suggest that bugs that crash the blockchain will be paid with 2 BTC if they inlude a full explanation, and a reproducible transaction/script/whatever! Lannsiter you would have to agree to do the payouts.

Happy hacking, and hopefully we find the next bug quick.

eB101

full member

Activity: 132

Merit: 100

Quote from: xxxgoodgirls on August 31, 2016, 08:14:51 PM

Quote from: eB101 on August 31, 2016, 05:23:57 PM

Hi, I'm hoping someone can help.

I participated in early phase with 0.8BTC, however on the website I can't find my BTC address. Is there another place we are supposed to check?

Transaction:
https://blockchain.info/tx-index/0e1307c7b7c024b0b67afcbadfe41adafe1be5b595e1ead31f5b522b665a606f

Will appreciate any help.

https://github.com/elastic-project/genesis-block/blob/master/genesis-block.json

Code:

{
"btc_amount": 0.8,
"mir_amount": 5944.691358024691,
"btc_tx": "0e1307c7b7c024b0b67afcbadfe41adafe1be5b595e1ead31f5b522b665a606f",
"btc_block": 403688,
"owner_pubkey": "0340217d42da4867ccc974fc17bb0bb8e991329cad384bf15fb5826632d4f8177a"
},

there

Thanks! I'm assuming there is nothing else to do at the moment (and that we don't have access to those yet)

cyberhacker

legendary

Activity: 1330

Merit: 1000

@lannister @EK，

can you put a QQ group: 108972650 in oP? there is a bunch of chinese fans, and they need something like slack channel.

thanks.

xxxgoodgirls

legendary

Activity: 1092

Merit: 1001

Quote from: eB101 on August 31, 2016, 05:23:57 PM

Hi, I'm hoping someone can help.

I participated in early phase with 0.8BTC, however on the website I can't find my BTC address. Is there another place we are supposed to check?

Transaction:
https://blockchain.info/tx-index/0e1307c7b7c024b0b67afcbadfe41adafe1be5b595e1ead31f5b522b665a606f

Will appreciate any help.

https://github.com/elastic-project/genesis-block/blob/master/genesis-block.json

Code:

{
"btc_amount": 0.8,
"mir_amount": 5944.691358024691,
"btc_tx": "0e1307c7b7c024b0b67afcbadfe41adafe1be5b595e1ead31f5b522b665a606f",
"btc_block": 403688,
"owner_pubkey": "0340217d42da4867ccc974fc17bb0bb8e991329cad384bf15fb5826632d4f8177a"
},

there

eB101

full member

Activity: 132

Merit: 100

Hi, I'm hoping someone can help.

I participated in early phase with 0.8BTC, however on the website I can't find my BTC address. Is there another place we are supposed to check?

Transaction:
https://blockchain.info/tx-index/0e1307c7b7c024b0b67afcbadfe41adafe1be5b595e1ead31f5b522b665a606f

Will appreciate any help.

Evil-Knievel

legendary

Activity: 1260

Merit: 1168

First bug has been found, it looks like Wink

Would be great if the one who did it remembered what he did! There should be a bug bounty for that!
I am checking and pushing a fix in a short while!

trader19

legendary

Activity: 1232

Merit: 1001

so we are stuck at block 670 Huh

25/07/2014 23:30:49 (2 years back) Grin

how long have you been workin on this project EK? JK
i wanted to start forging but as long as we are stuck it gets refused, i guess we can only wait!?

13Darko

hero member

Activity: 621

Merit: 507

Radix-The Decentralized Finance Protocol

Quote from: Free_Crypto on August 31, 2016, 09:18:41 AM

how will you beat golem project? they have the same idea like u. may be lanister can tell to us some differnce from that project. I know that he also made some research about it

Has Golem at least anything to show to the public? Any working code? Here we have a testnet already.

unvoid

hero member

Activity: 535

Merit: 500

@ImI looks like your node is trying to cancel my work but it can't because it's already finished.

Cryptorials

hero member

Activity: 690

Merit: 505

Cryptorials.io

Looks like this thing is getting close to launch, good stuff!

wpalczynski

legendary

Activity: 1456

Merit: 1000

Quote from: cyberhacker on August 31, 2016, 10:55:56 AM

is that a serious problem?

Its just testnet, no problems are serious and will be fixed.

cyberhacker

legendary

Activity: 1330

Merit: 1000

is that a serious problem?

ImI

legendary

Activity: 1946

Merit: 1019

Quote from: unvoid on August 31, 2016, 10:49:13 AM

Quote from: ImI on August 31, 2016, 10:01:49 AM

Quote from: unvoid on August 31, 2016, 06:32:46 AM

And network stuck.

@XEL-9HQ9-BXCV-TARZ-BRDNA please don't stop forging for at least 24h until other nodes coins get mature (1440 blocks min. from the moment they will receive coins) because if you aren't forging rest of the network is stopped and there is nothing we can do with test-net.

the "trustworthy member" is me. Grin

i accessed the account via http://52.57.12.123:6876/index.html. forging seems to be stuck at block#670.

i installed the git at my own server and got the same problem.

Quote

LIST OF OVERLOADED POW TRANSACTIONS IN BLOCK CREATION
*****************************************************
   5403457228271962868
LIST OF OVERLOADED BOUNTY TRANSACTIONS IN BLOCK CREATION
********************************************************
   5403457228271962868
Work 5403457228271962868 has gotten 5 bounties.
nxt.NxtException$NotValidException: Cannot cancel already cancelled or finished work
   at nxt.TransactionType$WorkControl$2.validateAttachment(TransactionType.java:471)
   at nxt.Attachment$AbstractAttachment.validate(Attachment.java:34)
   at nxt.TransactionImpl.validate(TransactionImpl.java:835)
   at nxt.WorkLogicManager.createOffTheRecordZeroFeeTransaction(WorkLogicManager.java:1442)
   at nxt.BlockchainProcessorImpl.generateBlock(BlockchainProcessorImpl.java:1158)
   at nxt.Generator.forge(Generator.java:296)
   at nxt.Generator$1.run(Generator.java:79)
   at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
   at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
   at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
   at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
   at java.lang.Thread.run(Thread.java:745)
2016-08-31 14:41:25 FINE: Generator$1.run: Error in block generation thread
nxt.BlockchainProcessor$BlockNotAcceptedException: Could not create block, ie, the transaction that MUST be included due to timeout / bounty / refund.
   at nxt.BlockchainProcessorImpl.generateBlock(BlockchainProcessorImpl.java:1165)
   at nxt.Generator.forge(Generator.java:296)
   at nxt.Generator$1.run(Generator.java:79)
   at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
   at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
   at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
   at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
   at java.lang.Thread.run(Thread.java:745)

So we have first serious bug. It's my fault and I'm pround!

You get this exception after I submitted work to the network.

Well done! As reward you will get 10m Test-XEL. Grin

unvoid

hero member

Activity: 535

Merit: 500

Quote from: ImI on August 31, 2016, 10:01:49 AM

Quote from: unvoid on August 31, 2016, 06:32:46 AM

And network stuck.

@XEL-9HQ9-BXCV-TARZ-BRDNA please don't stop forging for at least 24h until other nodes coins get mature (1440 blocks min. from the moment they will receive coins) because if you aren't forging rest of the network is stopped and there is nothing we can do with test-net.

the "trustworthy member" is me. Grin

i accessed the account via http://52.57.12.123:6876/index.html. forging seems to be stuck at block#670.

i installed the git at my own server and got the same problem.

Quote

LIST OF OVERLOADED POW TRANSACTIONS IN BLOCK CREATION
*****************************************************
   5403457228271962868
LIST OF OVERLOADED BOUNTY TRANSACTIONS IN BLOCK CREATION
********************************************************
   5403457228271962868
Work 5403457228271962868 has gotten 5 bounties.
nxt.NxtException$NotValidException: Cannot cancel already cancelled or finished work
   at nxt.TransactionType$WorkControl$2.validateAttachment(TransactionType.java:471)
   at nxt.Attachment$AbstractAttachment.validate(Attachment.java:34)
   at nxt.TransactionImpl.validate(TransactionImpl.java:835)
   at nxt.WorkLogicManager.createOffTheRecordZeroFeeTransaction(WorkLogicManager.java:1442)
   at nxt.BlockchainProcessorImpl.generateBlock(BlockchainProcessorImpl.java:1158)
   at nxt.Generator.forge(Generator.java:296)
   at nxt.Generator$1.run(Generator.java:79)
   at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
   at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
   at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
   at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
   at java.lang.Thread.run(Thread.java:745)
2016-08-31 14:41:25 FINE: Generator$1.run: Error in block generation thread
nxt.BlockchainProcessor$BlockNotAcceptedException: Could not create block, ie, the transaction that MUST be included due to timeout / bounty / refund.
   at nxt.BlockchainProcessorImpl.generateBlock(BlockchainProcessorImpl.java:1165)
   at nxt.Generator.forge(Generator.java:296)
   at nxt.Generator$1.run(Generator.java:79)
   at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
   at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
   at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
   at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
   at java.lang.Thread.run(Thread.java:745)

So we have first serious bug. It's my fault and I'm pround!

You get this exception after I submitted work to the network.

tomkat

hero member

Activity: 1022

Merit: 507

Quote from: ImI on August 31, 2016, 09:37:39 AM

Quote from: Free_Crypto on August 31, 2016, 09:18:41 AM

how will you beat golem project? they have the same idea like u. may be lanister can tell to us some differnce from that project. I know that he also made some research about it

you could also ask: how will golem beat us?

from an investor point-of-view golem is very expensive, they are selling for 5mio$. but you wont get shares of the actual project but instead just get some kind of profit-payment-token. its similar like JINN where investors just get some parts of the profits and the actual company is owned by devs/earlyinvestors.

that being said Golem wont have to necessarily "beat" us as much as we dont have to necessarily beat them. in crypto its common that projects that try to achieve something similar ar both valued dozens or even hundreds of $-millions. just scroll through the top100 marketcap listings and you will fînd dozens of projects that try to achieve basically the same thing. its no problem at all! projects can learn from and inspire each other and create a win/win situation longterm.

justmy2xel.

edit: or in other words if golem gets a marketcap of 100m and we get a marketcap of 20m i think there is no reason to complain from an investor pov.

http://www.golemproject.net/doc/GolemNanopayments.pdf
Quote "This makes Ethereum our platform of choice for implementation of micropayment schemes."

So Golem will be using ETH, and their own GNT token as its currency.
https://blog.golemproject.net/golem-network-token-gnt-sale-220c2a732f9#.jrlb6xnzm

Golem seems to be initially focused on CGI rendering (for Blender users).

Quote "The current version of Golem is only focused on rendering in Blender and although it will be useful to CGI artists, we consider CGI rendering to be primarily a proof of concept and training ground. After a full cycle of tests, Brass Golem will be released in Autumn this year. Even though we do not expect that blender CGI rendering will create enough turnover to justify all the work we have put in the project, this will be the first decentralised computing power market and at the same time (most likely) the first thing you will be able to pay for with your Ethers."

And (as of now) they don't see other decentralized supercomputers (like Elastic) as competitors

Quote "Our real competitors are Amazon Web Services, Google Cloud and other cloud providers. Our aim is to provide similar functionality at much lower prices."

ImI

legendary

Activity: 1946

Merit: 1019

Quote from: unvoid on August 31, 2016, 06:32:46 AM

And network stuck.

@XEL-9HQ9-BXCV-TARZ-BRDNA please don't stop forging for at least 24h until other nodes coins get mature (1440 blocks min. from the moment they will receive coins) because if you aren't forging rest of the network is stopped and there is nothing we can do with test-net.

the "trustworthy member" is me. Grin

i accessed the account via http://52.57.12.123:6876/index.html. forging seems to be stuck at block#670.

i installed the git at my own server and got the same problem.

Quote

LIST OF OVERLOADED POW TRANSACTIONS IN BLOCK CREATION
*****************************************************
   5403457228271962868
LIST OF OVERLOADED BOUNTY TRANSACTIONS IN BLOCK CREATION
********************************************************
   5403457228271962868
Work 5403457228271962868 has gotten 5 bounties.
nxt.NxtException$NotValidException: Cannot cancel already cancelled or finished work
   at nxt.TransactionType$WorkControl$2.validateAttachment(TransactionType.java:471)
   at nxt.Attachment$AbstractAttachment.validate(Attachment.java:34)
   at nxt.TransactionImpl.validate(TransactionImpl.java:835)
   at nxt.WorkLogicManager.createOffTheRecordZeroFeeTransaction(WorkLogicManager.java:1442)
   at nxt.BlockchainProcessorImpl.generateBlock(BlockchainProcessorImpl.java:1158)
   at nxt.Generator.forge(Generator.java:296)
   at nxt.Generator$1.run(Generator.java:79)
   at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
   at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
   at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
   at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
   at java.lang.Thread.run(Thread.java:745)
2016-08-31 14:41:25 FINE: Generator$1.run: Error in block generation thread
nxt.BlockchainProcessor$BlockNotAcceptedException: Could not create block, ie, the transaction that MUST be included due to timeout / bounty / refund.
   at nxt.BlockchainProcessorImpl.generateBlock(BlockchainProcessorImpl.java:1165)
   at nxt.Generator.forge(Generator.java:296)
   at nxt.Generator$1.run(Generator.java:79)
   at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
   at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
   at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
   at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
   at java.lang.Thread.run(Thread.java:745)

ImI

legendary

Activity: 1946

Merit: 1019

Quote from: Free_Crypto on August 31, 2016, 09:18:41 AM

how will you beat golem project? they have the same idea like u. may be lanister can tell to us some differnce from that project. I know that he also made some research about it

you could also ask: how will golem beat us?

from an investor point-of-view golem is very expensive, they are selling for 5mio$. but you wont get shares of the actual project but instead just get some kind of profit-payment-token. its similar like JINN where investors just get some parts of the profits and the actual company is owned by devs/earlyinvestors.

that being said Golem wont have to necessarily "beat" us as much as we dont have to necessarily beat them. in crypto its common that projects that try to achieve something similar ar both valued dozens or even hundreds of $-millions. just scroll through the top100 marketcap listings and you will fînd dozens of projects that try to achieve basically the same thing. its no problem at all! projects can learn from and inspire each other and create a win/win situation longterm.

justmy2xel.

edit: or in other words if golem gets a marketcap of 100m and we get a marketcap of 20m i think there is no reason to complain from an investor pov.

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