Topic: [ANN][XEL] Elastic Project - The Decentralized Supercomputer - page 254. (Read 450524 times)
September 16, 2016, 03:33:30 PM
sent some to unvoid
September 16, 2016, 03:29:37 PM
@EK, we still have old problem. When there is some work in the network someone is banned hard (ending on fork). It's easy to recreate this in your env. Just put work after work to the network. you'll see that after some time you'll end on a fork because everyone else will ban you.
September 16, 2016, 03:28:00 PM
i just logged in at XEL-9HQ9-BXCV-TARZ-BRDNA and checked. forging seems OK.
September 16, 2016, 03:27:47 PM
i just logged in at XEL-9HQ9-BXCV-TARZ-BRDNA and checked. forging seems OK.
Because you're on a fork.
September 16, 2016, 03:24:17 PM
i just logged in at XEL-9HQ9-BXCV-TARZ-BRDNA and checked. forging seems OK.
September 16, 2016, 02:43:15 PM
(snip)
I need to think up a example to try out EPL on so if anyone has any suggestions for a use case, please let me know.
I need to think up a example to try out EPL on so if anyone has any suggestions for a use case, please let me know.
You guys should play chess against each other, using XEL to determine the next moves (so basically, XEL would play chess against itself)
September 16, 2016, 02:20:26 PM
Long diff retargeting times? Did you see this @EK? At new version when XEL-9HQ9-BXCV-TARZ-BRDNA was forging with his big stack he was forging couple blocks per min. When XEL-9HQ9-BXCV-TARZ-BRDNA disappeared XEL-K3TA-MQNB-4NHD-5GE8U is the only one forging and he have trouble to get block in 5 min. Anything changes in that matter with new versions of NXT?
thats me forging, i believe ImI stopped forging blocks after he submitted work to network.. this is what my logs are showing. Code:
2016-09-16 17:36:45 FINE: Failed to parse block: {"totalFeeNQT":100000000,"previousBlockHash":"8eacf387575ba59f4208bb56cd8d60466cf1c26d9847c59a67043a0a1ab3b9bb","payloadLength":570,"previousBlock":"11503701254688976014","totalAmountNQT":22200000000,"generationSignature":"8547a8ad19f4bac3e3f4ec3a9ba9d26ea9f0711d01e50d1a95ce2018823384cc","generatorPublicKey":"15d039ed644401856cf294e475cc9b9ed1d8abbf8393435f89f4ab484faa0e2e","payloadHash":"eabb9817fee110eaf52b145c147ce3c089f961a6afded643a6acb188001bc19c","blockSignature":"01982fcf547532eb8aa897e88d2e297bd5dd9a2fb436fcc2002f37fe445afe0bfb28bb498a9a5f41fcbb841f6292a8e7f6a01cea4fb19bb3556f2504d52ff42e","transactions":[{"senderPublicKey":"d9d5c57971eefb085e3abaf7a5a4a6cdb8185f30105583cdb09ad8f61886ec65","attachment":{"xel_per_pow":1000000000,"percentage_pow_fund":60,"bountyLimit":10,"title":"Test work","deadline":250,"version.WorkCreation":1},"subtype":0,"amountNQT":22200000000,"signature":"e068f6133f9a49b253e7a21f120981c2146957f84415daa374d29b3191b9cf06663c5b48fa3b3ec00a5e36e45f88097bc18f7ad1a3a43e6d3a1db4bcba897423","feeNQT":100000000,"ecBlockHeight":786,"type":3,"deadline":1440,"version":1,"timestamp":88742073,"ecBlockId":"12297225825676462765"}],"version":1,"timestamp":88742090}
2016-09-16 17:36:45 FINE: Failed to parse block: nxt.NxtException$NotValidException: Invalid transaction signature for transaction {"senderPublicKey":"d9d5c57971eefb085e3abaf7a5a4a6cdb8185f30105583cdb09ad8f61886ec65","attachment":{"xel_per_pow":1000000000,"percentage_pow_fund":60,"bountyLimit":10,"title":"Test work","deadline":250,"version.WorkCreation":1},"subtype":0,"amountNQT":22200000000,"signature":"e068f6133f9a49b253e7a21f120981c2146957f84415daa374d29b3191b9cf06663c5b48fa3b3ec00a5e36e45f88097bc18f7ad1a3a43e6d3a1db4bcba897423","feeNQT":100000000,"ecBlockHeight":786,"type":3,"deadline":1440,"version":1,"timestamp":88742073,"ecBlockId":"12297225825676462765"}
nxt.NxtException$NotValidException: Invalid transaction signature for transaction {"senderPublicKey":"d9d5c57971eefb085e3abaf7a5a4a6cdb8185f30105583cdb09ad8f61886ec65","attachment":{"xel_per_pow":1000000000,"percentage_pow_fund":60,"bountyLimit":10,"title":"Test work","deadline":250,"version.WorkCreation":1},"subtype":0,"amountNQT":22200000000,"signature":"e068f6133f9a49b253e7a21f120981c2146957f84415daa374d29b3191b9cf06663c5b48fa3b3ec00a5e36e45f88097bc18f7ad1a3a43e6d3a1db4bcba897423","feeNQT":100000000,"ecBlockHeight":786,"type":3,"deadline":1440,"version":1,"timestamp":88742073,"ecBlockId":"12297225825676462765"}
at nxt.TransactionImpl.parseTransaction(TransactionImpl.java:816)
at nxt.BlockImpl.parseBlock(BlockImpl.java:288)
at nxt.BlockchainProcessorImpl$GetNextBlocks.call(BlockchainProcessorImpl.java:707)
at nxt.BlockchainProcessorImpl$GetNextBlocks.call(BlockchainProcessorImpl.java:628)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
2016-09-16 17:36:45 FINE: Blacklisting 52.57.31.137 because of: nxt.NxtException$NotValidException: Invalid transaction signature for transaction {"senderPublicKey":"d9d5c57971eefb085e3abaf7a5a4a6cdb8185f30105583cdb09ad8f61886ec65","attachment":{"xel_per_pow":1000000000,"percentage_pow_fund":60,"bountyLimit":10,"title":"Test work","deadline":250,"version.WorkCreation":1},"subtype":0,"amountNQT":22200000000,"signature":"e068f6133f9a49b253e7a21f120981c2146957f84415daa374d29b3191b9cf06663c5b48fa3b3ec00a5e36e45f88097bc18f7ad1a3a43e6d3a1db4bcba897423","feeNQT":100000000,"ecBlockHeight":786,"type":3,"deadline":1440,"version":1,"timestamp":88742073,"ecBlockId":"12297225825676462765"}
nxt.NxtException$NotValidException: Invalid transaction signature for transaction {"senderPublicKey":"d9d5c57971eefb085e3abaf7a5a4a6cdb8185f30105583cdb09ad8f61886ec65","attachment":{"xel_per_pow":1000000000,"percentage_pow_fund":60,"bountyLimit":10,"title":"Test work","deadline":250,"version.WorkCreation":1},"subtype":0,"amountNQT":22200000000,"signature":"e068f6133f9a49b253e7a21f120981c2146957f84415daa374d29b3191b9cf06663c5b48fa3b3ec00a5e36e45f88097bc18f7ad1a3a43e6d3a1db4bcba897423","feeNQT":100000000,"ecBlockHeight":786,"type":3,"deadline":1440,"version":1,"timestamp":88742073,"ecBlockId":"12297225825676462765"}
2016-09-16 17:36:45 FINE: Failed to parse block: nxt.NxtException$NotValidException: Invalid transaction signature for transaction {"senderPublicKey":"d9d5c57971eefb085e3abaf7a5a4a6cdb8185f30105583cdb09ad8f61886ec65","attachment":{"xel_per_pow":1000000000,"percentage_pow_fund":60,"bountyLimit":10,"title":"Test work","deadline":250,"version.WorkCreation":1},"subtype":0,"amountNQT":22200000000,"signature":"e068f6133f9a49b253e7a21f120981c2146957f84415daa374d29b3191b9cf06663c5b48fa3b3ec00a5e36e45f88097bc18f7ad1a3a43e6d3a1db4bcba897423","feeNQT":100000000,"ecBlockHeight":786,"type":3,"deadline":1440,"version":1,"timestamp":88742073,"ecBlockId":"12297225825676462765"}
nxt.NxtException$NotValidException: Invalid transaction signature for transaction {"senderPublicKey":"d9d5c57971eefb085e3abaf7a5a4a6cdb8185f30105583cdb09ad8f61886ec65","attachment":{"xel_per_pow":1000000000,"percentage_pow_fund":60,"bountyLimit":10,"title":"Test work","deadline":250,"version.WorkCreation":1},"subtype":0,"amountNQT":22200000000,"signature":"e068f6133f9a49b253e7a21f120981c2146957f84415daa374d29b3191b9cf06663c5b48fa3b3ec00a5e36e45f88097bc18f7ad1a3a43e6d3a1db4bcba897423","feeNQT":100000000,"ecBlockHeight":786,"type":3,"deadline":1440,"version":1,"timestamp":88742073,"ecBlockId":"12297225825676462765"}
at nxt.TransactionImpl.parseTransaction(TransactionImpl.java:816)
at nxt.BlockImpl.parseBlock(BlockImpl.java:288)
at nxt.BlockchainProcessorImpl$GetNextBlocks.call(BlockchainProcessorImpl.java:707)
at nxt.BlockchainProcessorImpl$GetNextBlocks.call(BlockchainProcessorImpl.java:628)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
2016-09-16 17:36:45 FINE: Blacklisting 52.57.31.137 because of: nxt.NxtException$NotValidException: Invalid transaction signature for transaction {"senderPublicKey":"d9d5c57971eefb085e3abaf7a5a4a6cdb8185f30105583cdb09ad8f61886ec65","attachment":{"xel_per_pow":1000000000,"percentage_pow_fund":60,"bountyLimit":10,"title":"Test work","deadline":250,"version.WorkCreation":1},"subtype":0,"amountNQT":22200000000,"signature":"e068f6133f9a49b253e7a21f120981c2146957f84415daa374d29b3191b9cf06663c5b48fa3b3ec00a5e36e45f88097bc18f7ad1a3a43e6d3a1db4bcba897423","feeNQT":100000000,"ecBlockHeight":786,"type":3,"deadline":1440,"version":1,"timestamp":88742073,"ecBlockId":"12297225825676462765"}
nxt.NxtException$NotValidException: Invalid transaction signature for transaction {"senderPublicKey":"d9d5c57971eefb085e3abaf7a5a4a6cdb8185f30105583cdb09ad8f61886ec65","attachment":{"xel_per_pow":1000000000,"percentage_pow_fund":60,"bountyLimit":10,"title":"Test work","deadline":250,"version.WorkCreation":1},"subtype":0,"amountNQT":22200000000,"signature":"e068f6133f9a49b253e7a21f120981c2146957f84415daa374d29b3191b9cf06663c5b48fa3b3ec00a5e36e45f88097bc18f7ad1a3a43e6d3a1db4bcba897423","feeNQT":100000000,"ecBlockHeight":786,"type":3,"deadline":1440,"version":1,"timestamp":88742073,"ecBlockId":"12297225825676462765"}
September 16, 2016, 02:14:31 PM
Hi EK, I've spent some time reviewing the EPL logic and I think I am understanding it. However, just to clarify, to me it looks like everything is a 32 bit operation. For example I don't see any carry-save logic in the AddNode module for larger values and the shifters all look to be 32 bit as well. Is there a plan to add functionality to allow larger operations, or did I just mis-interpret how your code works.
Also, as someone asked before about looping, I looked at the Repeat module and to me it looks like it would repeat a single operation, but not a group of operations, is that correct?
I need to think up a example to try out EPL on so if anyone has any suggestions for a use case, please let me know.
Also, as someone asked before about looping, I looked at the Repeat module and to me it looks like it would repeat a single operation, but not a group of operations, is that correct?
I need to think up a example to try out EPL on so if anyone has any suggestions for a use case, please let me know.
Awesome question. Bump.
September 16, 2016, 02:06:26 PM
Long diff retargeting times? Did you see this @EK? At new version when XEL-9HQ9-BXCV-TARZ-BRDNA was forging with his big stack he was forging couple blocks per min. When XEL-9HQ9-BXCV-TARZ-BRDNA disappeared XEL-K3TA-MQNB-4NHD-5GE8U is the only one forging and he have trouble to get block in 5 min. Anything changes in that matter with new versions of NXT?
Are they (NXT) was afraid of split (like ETH/ETC)? So they did long times of retargeting to be sure that one chain (weaker) will be long behind?
Are they (NXT) was afraid of split (like ETH/ETC)? So they did long times of retargeting to be sure that one chain (weaker) will be long behind?
September 16, 2016, 01:47:50 PM
September 16, 2016, 01:43:11 PM
@ImI XEL-7UTR-VYZY-ZUZZ-DTJJ5
Thanks!
Thanks!
September 16, 2016, 01:42:00 PM
Code:
2016-09-16 20:40:33 FINE: Failed to parse block: nxt.NxtException$NotValidException: Invalid transaction signature for transaction {"senderPublicKey":"d9d5c57971eefb085e3abaf7a5a4a6cdb8185f30105583cdb09ad8f61886ec65","attachment":{"xel_per_pow":1000000000,"percentage_pow_fund":60,"bountyLimit":10,"title":"Test work","deadline":250,"version.WorkCreation":1},"subtype":0,"amountNQT":22200000000,"signature":"e068f6133f9a49b253e7a21f120981c2146957f84415daa374d29b3191b9cf06663c5b48fa3b3ec00a5e36e45f88097bc18f7ad1a3a43e6d3a1db4bcba897423","feeNQT":100000000,"ecBlockHeight":786,"type":3,"deadline":1440,"version":1,"timestamp":88742073,"ecBlockId":"12297225825676462765"}
nxt.NxtException$NotValidException: Invalid transaction signature for transaction {"senderPublicKey":"d9d5c57971eefb085e3abaf7a5a4a6cdb8185f30105583cdb09ad8f61886ec65","attachment":{"xel_per_pow":1000000000,"percentage_pow_fund":60,"bountyLimit":10,"title":"Test work","deadline":250,"version.WorkCreation":1},"subtype":0,"amountNQT":22200000000,"signature":"e068f6133f9a49b253e7a21f120981c2146957f84415daa374d29b3191b9cf06663c5b48fa3b3ec00a5e36e45f88097bc18f7ad1a3a43e6d3a1db4bcba897423","feeNQT":100000000,"ecBlockHeight":786,"type":3,"deadline":1440,"version":1,"timestamp":88742073,"ecBlockId":"12297225825676462765"}
at nxt.TransactionImpl.parseTransaction(TransactionImpl.java:816)
at nxt.BlockImpl.parseBlock(BlockImpl.java:288)
at nxt.BlockchainProcessorImpl$GetNextBlocks.call(BlockchainProcessorImpl.java:707)
at nxt.BlockchainProcessorImpl$GetNextBlocks.call(BlockchainProcessorImpl.java:628)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
2016-09-16 20:40:33 FINE: Blacklisting 52.28.123.208 because of: nxt.NxtException$NotValidException: Invalid transaction signature for transaction {"senderPublicKey":"d9d5c57971eefb085e3abaf7a5a4a6cdb8185f30105583cdb09ad8f61886ec65","attachment":{"xel_per_pow":1000000000,"percentage_pow_fund":60,"bountyLimit":10,"title":"Test work","deadline":250,"version.WorkCreation":1},"subtype":0,"amountNQT":22200000000,"signature":"e068f6133f9a49b253e7a21f120981c2146957f84415daa374d29b3191b9cf06663c5b48fa3b3ec00a5e36e45f88097bc18f7ad1a3a43e6d3a1db4bcba897423","feeNQT":100000000,"ecBlockHeight":786,"type":3,"deadline":1440,"version":1,"timestamp":88742073,"ecBlockId":"12297225825676462765"}
nxt.NxtException$NotValidException: Invalid transaction signature for transaction {"senderPublicKey":"d9d5c57971eefb085e3abaf7a5a4a6cdb8185f30105583cdb09ad8f61886ec65","attachment":{"xel_per_pow":1000000000,"percentage_pow_fund":60,"bountyLimit":10,"title":"Test work","deadline":250,"version.WorkCreation":1},"subtype":0,"amountNQT":22200000000,"signature":"e068f6133f9a49b253e7a21f120981c2146957f84415daa374d29b3191b9cf06663c5b48fa3b3ec00a5e36e45f88097bc18f7ad1a3a43e6d3a1db4bcba897423","feeNQT":100000000,"ecBlockHeight":786,"type":3,"deadline":1440,"version":1,"timestamp":88742073,"ecBlockId":"12297225825676462765"}
at nxt.TransactionImpl.parseTransaction(TransactionImpl.java:816)
at nxt.BlockImpl.parseBlock(BlockImpl.java:288)
at nxt.BlockchainProcessorImpl$GetNextBlocks.call(BlockchainProcessorImpl.java:707)
at nxt.BlockchainProcessorImpl$GetNextBlocks.call(BlockchainProcessorImpl.java:628)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
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)
nxt.NxtException$NotValidException: Invalid transaction signature for transaction {"senderPublicKey":"d9d5c57971eefb085e3abaf7a5a4a6cdb8185f30105583cdb09ad8f61886ec65","attachment":{"xel_per_pow":1000000000,"percentage_pow_fund":60,"bountyLimit":10,"title":"Test work","deadline":250,"version.WorkCreation":1},"subtype":0,"amountNQT":22200000000,"signature":"e068f6133f9a49b253e7a21f120981c2146957f84415daa374d29b3191b9cf06663c5b48fa3b3ec00a5e36e45f88097bc18f7ad1a3a43e6d3a1db4bcba897423","feeNQT":100000000,"ecBlockHeight":786,"type":3,"deadline":1440,"version":1,"timestamp":88742073,"ecBlockId":"12297225825676462765"}
at nxt.TransactionImpl.parseTransaction(TransactionImpl.java:816)
at nxt.BlockImpl.parseBlock(BlockImpl.java:288)
at nxt.BlockchainProcessorImpl$GetNextBlocks.call(BlockchainProcessorImpl.java:707)
at nxt.BlockchainProcessorImpl$GetNextBlocks.call(BlockchainProcessorImpl.java:628)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
2016-09-16 20:40:33 FINE: Blacklisting 52.28.123.208 because of: nxt.NxtException$NotValidException: Invalid transaction signature for transaction {"senderPublicKey":"d9d5c57971eefb085e3abaf7a5a4a6cdb8185f30105583cdb09ad8f61886ec65","attachment":{"xel_per_pow":1000000000,"percentage_pow_fund":60,"bountyLimit":10,"title":"Test work","deadline":250,"version.WorkCreation":1},"subtype":0,"amountNQT":22200000000,"signature":"e068f6133f9a49b253e7a21f120981c2146957f84415daa374d29b3191b9cf06663c5b48fa3b3ec00a5e36e45f88097bc18f7ad1a3a43e6d3a1db4bcba897423","feeNQT":100000000,"ecBlockHeight":786,"type":3,"deadline":1440,"version":1,"timestamp":88742073,"ecBlockId":"12297225825676462765"}
nxt.NxtException$NotValidException: Invalid transaction signature for transaction {"senderPublicKey":"d9d5c57971eefb085e3abaf7a5a4a6cdb8185f30105583cdb09ad8f61886ec65","attachment":{"xel_per_pow":1000000000,"percentage_pow_fund":60,"bountyLimit":10,"title":"Test work","deadline":250,"version.WorkCreation":1},"subtype":0,"amountNQT":22200000000,"signature":"e068f6133f9a49b253e7a21f120981c2146957f84415daa374d29b3191b9cf06663c5b48fa3b3ec00a5e36e45f88097bc18f7ad1a3a43e6d3a1db4bcba897423","feeNQT":100000000,"ecBlockHeight":786,"type":3,"deadline":1440,"version":1,"timestamp":88742073,"ecBlockId":"12297225825676462765"}
at nxt.TransactionImpl.parseTransaction(TransactionImpl.java:816)
at nxt.BlockImpl.parseBlock(BlockImpl.java:288)
at nxt.BlockchainProcessorImpl$GetNextBlocks.call(BlockchainProcessorImpl.java:707)
at nxt.BlockchainProcessorImpl$GetNextBlocks.call(BlockchainProcessorImpl.java:628)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
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)
During new blockchain download.
September 16, 2016, 01:25:30 PM
Hi EK, I've spent some time reviewing the EPL logic and I think I am understanding it. However, just to clarify, to me it looks like everything is a 32 bit operation. For example I don't see any carry-save logic in the AddNode module for larger values and the shifters all look to be 32 bit as well. Is there a plan to add functionality to allow larger operations, or did I just mis-interpret how your code works.
Also, as someone asked before about looping, I looked at the Repeat module and to me it looks like it would repeat a single operation, but not a group of operations, is that correct?
I need to think up a example to try out EPL on so if anyone has any suggestions for a use case, please let me know.
Also, as someone asked before about looping, I looked at the Repeat module and to me it looks like it would repeat a single operation, but not a group of operations, is that correct?
I need to think up a example to try out EPL on so if anyone has any suggestions for a use case, please let me know.
September 16, 2016, 10:59:01 AM
wow. Two days away and lot of changes! I was trying to read for last two days but had no time to write something. Actually right now also can't be here longer but I want to just write:
Great work @EK!
and I'll try maybe later this day to download client, update explorer, read posts etc.
Again, awesome job, lot of new code, ideas and great current result. Can't wait to find time for all this stuff.
I was trying to read for last two days but had no time to write something. Actually right now also can't be here longer but I want to just write:Great work @EK!
and I'll try maybe later this day to download client, update explorer, read posts etc.
Again, awesome job, lot of new code, ideas and great current result. Can't wait to find time for all this stuff.
September 16, 2016, 09:37:01 AM
Remember guys,
the testnet is not yet "officially" live! Those who have been running the elastic-core development branch will need to frequently do a "git pull; ./compile.sh" as many things still change.
This is the case now: we need to hard fork the pre-testnet! Only nodes with version 0.3.2 are allowed to connect.
A git pull, followed by a recompile is enough in most cases! if problems arise (or if you want to be on the safe side), just redownload the chain by issuing a rm -rf nxt_test_db/
Only test the pre-pre-testnet if you like "hacking around".
the testnet is not yet "officially" live! Those who have been running the elastic-core development branch will need to frequently do a "git pull; ./compile.sh" as many things still change.
This is the case now: we need to hard fork the pre-testnet! Only nodes with version 0.3.2 are allowed to connect.
A git pull, followed by a recompile is enough in most cases! if problems arise (or if you want to be on the safe side), just redownload the chain by issuing a rm -rf nxt_test_db/
Only test the pre-pre-testnet if you like "hacking around".
September 16, 2016, 06:48:18 AM
If so, someone can send back some testXEL? Thanks
XEL-6R66-2MZY-MA5N-7Y23F
XEL-6R66-2MZY-MA5N-7Y23F
sent
September 16, 2016, 06:47:04 AM
@ImI can i have some coins so i can forge, thanks.
Code:
XEL-K3TA-MQNB-4NHD-5GE8U
sent
September 16, 2016, 03:56:42 AM
Today, the last few missing pieces regarding the UI will come. I have loaded more on the "test" account btw 
Also, I started to work on the "Genesisblock Redeem" function. If anyone wants to join on this one, feel free!
The redeem transaction will be an own transaction type matching a SECP256k1 signature to an entry in the genesis block. To make it simple, I thought it would be nice to add a few "importers" into the ui which will generate private keys from various types of wallets and prepare the require signature automatically.
Also, I started to work on the "Genesisblock Redeem" function. If anyone wants to join on this one, feel free!
The redeem transaction will be an own transaction type matching a SECP256k1 signature to an entry in the genesis block. To make it simple, I thought it would be nice to add a few "importers" into the ui which will generate private keys from various types of wallets and prepare the require signature automatically.
September 16, 2016, 03:54:56 AM
Quote from: hagie
Yes Blockcahin was reseted - I only got some xel from the public node from EK , I'll share some .
Transaction on the way ..
I have sent you XEL 100k from the old version 0.2.3, I guess you will not come if you used the new version.
September 16, 2016, 03:47:32 AM
If you want to update XEL to the newest version:
Stop your node (CTRL + C)
Go to main directory of XEL and:
Code:
git pull origin master
./compile.sh
rm -rf nxt_test_db/
screen ./run.sh
./compile.sh
rm -rf nxt_test_db/
screen ./run.sh
This not work for me.
Make a fresh clone of this repository : https://github.com/OrdinaryDude/elastic-core.git
This is the new 0.3.1 develop git.
regards
Thanks!
Is new blockchain? I lost my testXEL
If so, someone can send back some testXEL? Thanks
XEL-6R66-2MZY-MA5N-7Y23F
Yes Blockcahin was reseted - I only got some xel from the public node from EK , I'll share some .
Transaction on the way ..
Jump to: