Also live: scaled forging.
The "forging power" does no longer only relate proportionally to the amount of XEL balance / total supply, but to the XEL balance / total redeemed coins.
So even if only one person redeems 1 XEL, and the 99999999 XEL remain unclaimed, this one person has the full network's forging power.
Topic: [ANN][XEL] Elastic Project - The Decentralized Supercomputer - page 212. (Read 450523 times)
November 22, 2016, 08:21:07 AM
November 22, 2016, 08:15:52 AM
Hi EK, I attempted to submit a job and got the following error in the UI.
"Script kiddie, stay home! Please refrain from pruning unpruneable data"
I don't know what it means, but it did make me laugh :-)
"Script kiddie, stay home! Please refrain from pruning unpruneable data"
I don't know what it means, but it did make me laugh :-)
Let me check ;-) Well the thing is, source code can be pruned to keep the blockchain small. Work with pruned source code always validates to CORRECT since we cannot check the validity anymore as the source code is no longer present. This is required to sync the blockchain correctly, ... when receiving work without source code.
I have added checks that pruned work must have a certain age to avoid some types of attack vectors where people might prune source code too early (meaning when the work is still live) and submit anything as a valid POW.
EDIT: FIXED!
November 22, 2016, 08:12:19 AM
My only question is whether or not this would cause numerous forks in the first couple of days. For example. If 100 people log in to redeem, and none of these 100 people are peers of each other, don't we have 100 forks? And if so, what happens to the people who redeemed that don't end up on the longest chain? Do they have to redeem again?
At the moment I don't think so since they all first have to sync the blockchain to perform transactions, and their blocks are as regular as any other block, means it connects to the top of the chain. The only problem I see is that the block time might be lower than 1 minute in the first 5000 blocks ... occasionally.
I will roll out a test net soon so we can try it out ;-) All I gotta do is migrate the public nodes to the new docker system.
November 22, 2016, 08:12:04 AM
Hi EK, I attempted to submit a job and got the following error in the UI.
"Script kiddie, stay home! Please refrain from pruning unpruneable data"
I don't know what it means, but it did make me laugh :-)
"Script kiddie, stay home! Please refrain from pruning unpruneable data"
I don't know what it means, but it did make me laugh :-)
November 22, 2016, 08:06:47 AM
Another "dirty hack" that I have added but which needs some discussion I think:
At the beginning nobody has any XELs, so nobody can forge (the REDEEM account which holds all XEL is prevented to do anything but to spend REDEEM transactions, no block mining, no work, nothing).
But when nobody can forge, none of the redeem transactons can become confirmed which again means nobody can forge blocks.
So I have added a "hacky rule":
If the block height is smaller than 5000 and the block contains at least one redeem transaction, then anyone can forge this block regardless of his XEL balance.
The hack automatically becomes inactive after the blockchain has a height higher then 5000.
This should help bootstrapping from "zero". What do you think?
At the beginning nobody has any XELs, so nobody can forge (the REDEEM account which holds all XEL is prevented to do anything but to spend REDEEM transactions, no block mining, no work, nothing).
But when nobody can forge, none of the redeem transactons can become confirmed which again means nobody can forge blocks.
So I have added a "hacky rule":
If the block height is smaller than 5000 and the block contains at least one redeem transaction, then anyone can forge this block regardless of his XEL balance.
The hack automatically becomes inactive after the blockchain has a height higher then 5000.
This should help bootstrapping from "zero". What do you think?
My only question is whether or not this would cause numerous forks in the first couple of days. For example. If 100 people log in to redeem, and none of these 100 people are peers of each other, don't we have 100 forks? And if so, what happens to the people who redeemed that don't end up on the longest chain? Do they have to redeem again?
November 22, 2016, 07:35:10 AM
Another "dirty hack" that I have added but which needs some discussion I think:
At the beginning nobody has any XELs, so nobody can forge (the REDEEM account which holds all XEL is prevented to do anything but to spend REDEEM transactions, no block mining, no work, nothing).
But when nobody can forge, none of the redeem transactons can become confirmed which again means nobody can forge blocks.
So I have added a "hacky rule":
If the block height is smaller than 5000 and the block contains at least one redeem transaction, then anyone can forge this block regardless of his XEL balance.
The hack automatically becomes inactive after the blockchain has a height higher then 5000.
This should help bootstrapping from "zero". What do you think?
At the beginning nobody has any XELs, so nobody can forge (the REDEEM account which holds all XEL is prevented to do anything but to spend REDEEM transactions, no block mining, no work, nothing).
But when nobody can forge, none of the redeem transactons can become confirmed which again means nobody can forge blocks.
So I have added a "hacky rule":
If the block height is smaller than 5000 and the block contains at least one redeem transaction, then anyone can forge this block regardless of his XEL balance.
The hack automatically becomes inactive after the blockchain has a height higher then 5000.
This should help bootstrapping from "zero". What do you think?
November 22, 2016, 07:24:21 AM
@coralreefer:
1. I have fixed the error, where POW submissions were invalid shortly after the work package was switched.
2. I have extended your miner by a longpolling function. Here, "new blocks" are detected immediately and not after the work polling timer times out. This should avoid that the miners work on outdated packages at all. The Pull Request is here: https://github.com/sprocket-fpga/xel_miner/pull/10
1. I have fixed the error, where POW submissions were invalid shortly after the work package was switched.
2. I have extended your miner by a longpolling function. Here, "new blocks" are detected immediately and not after the work polling timer times out. This should avoid that the miners work on outdated packages at all. The Pull Request is here: https://github.com/sprocket-fpga/xel_miner/pull/10
I really appreciate you adding this. Keep up the great work!
November 22, 2016, 07:03:15 AM
when it will release. any dates
November 22, 2016, 05:53:09 AM
i have an offer to elastic community ..i think elastic project need a new website for foundation.
Domain name is supercomputer.tech
What do u think?
Domain name is supercomputer.tech
What do u think?
It sounds very solid. Good domain name is one of the conditions for a successful project.
supercomputer.tech
still i didnt take this, if everyone like it, we can register and donate foundation (if it need)
Ek, please tell us ur opinion..
I appreciate the idea, but personally, I don't like it.
It's been the "Elastic project" for some time now, the same goes with "XEL" as units. I assume using supercomputer.tech comes with a namechange of the project? otherwise it wouldn't really make sense.
"Supercomputer" is weirdly generic. You would think that "Elastic Project" is, too, but somehow, I think it's not. "Elastic Project -- The Decentralized Supercomputer" sounds better to me than just "Supercomputer". There are a lot of so-called supercomputers out there.
Excessive rebranding is the sign of a weak coin. This project is still in its very beginning, so this argument doesn't really count, but I just want to put it out there, because you can see it all the time. Your coin doesn't get any attention? Rebranding.
What Elastic Project could use, however, is something like a corporate design. I could try to whip something up (I could even use the official Elastic logo, if I have to. As I wrote before, I'm not a fan. Sorry to whoever designed it).
November 22, 2016, 05:38:40 AM
@coralreefer:
1. I have fixed the error, where POW submissions were invalid shortly after the work package was switched.
2. I have extended your miner by a longpolling function. Here, "new blocks" are detected immediately and not after the work polling timer times out. This should avoid that the miners work on outdated packages at all. The Pull Request is here: https://github.com/sprocket-fpga/xel_miner/pull/10
1. I have fixed the error, where POW submissions were invalid shortly after the work package was switched.
2. I have extended your miner by a longpolling function. Here, "new blocks" are detected immediately and not after the work polling timer times out. This should avoid that the miners work on outdated packages at all. The Pull Request is here: https://github.com/sprocket-fpga/xel_miner/pull/10
November 21, 2016, 11:57:22 PM
we have to bring this to exchanges asap.
no, we don't.
haha i agree! Its all about the coin...not getting it on the exchanges... exchanges will come to us
November 21, 2016, 11:00:04 PM
i have an offer to elastic community ..i think elastic project need a new website for foundation.
Domain name is supercomputer.tech
What do u think?
Domain name is supercomputer.tech
What do u think?
It sounds very solid. Good domain name is one of the conditions for a successful project.
supercomputer.tech
still i didnt take this, if everyone like it, we can register and donate foundation (if it need)
Ek, please tell us ur opinion..
November 21, 2016, 10:47:40 PM
i have an offer to elastic community ..i think elastic project need a new website for foundation.
Domain name is supercomputer.tech
What do u think?
Domain name is supercomputer.tech
What do u think?
It sounds very solid. Good domain name is one of the conditions for a successful project.
November 21, 2016, 09:18:37 PM
we have to bring this to exchanges asap.
no, we don't.
November 21, 2016, 09:16:16 PM
we have to bring this to exchanges asap.
I smell a big movement in btc end of year
where is EK ? Any updates ? I smell a big movement in btc end of year
November 21, 2016, 07:01:38 PM
we have to bring this to exchanges asap.
I smell a big movement in btc end of year
I smell a big movement in btc end of year
November 21, 2016, 06:06:09 PM
I am glad I donated from strongcoin. I have control of my private keys...
November 21, 2016, 10:52:34 AM
I sent a donation, but I was a newb back then and I sent funds from my coinbase account. Evil said that it might not be a problem to receive my XEL. I've been trying to reach Lannister, but he doesn't answer his bitmessage. I have what ever proof he needs. I would hate to miss out on this project. 
November 21, 2016, 10:33:07 AM
i have an offer to elastic community ..i think elastic project need a new website for foundation.
Domain name is supercomputer.tech
What do u think?
Domain name is supercomputer.tech
What do u think?
November 21, 2016, 10:20:59 AM
Quote
Any way to next step?thx
the client cannot download any blockchain cause the mainnet hasnt launched yet. patience.
Jump to: