Short News: Behind the curtains, plans are being plotted to pull off a GPU miner ;-) One step closer to super-computer-market domination!
EK, you're our Satoshi ! Thank you for the great research . 
Topic: [ANN][XEL] Elastic Project - The Decentralized Supercomputer - page 208. (Read 450523 times)
November 25, 2016, 02:15:10 PM
November 25, 2016, 02:14:38 PM
Random thoughts - I have been working 13 hours straight today, and it's gonna be more, so I guess it's time for a break.
When we take a look at other projects, we see a long history of videos where developers do some jibber jabber, show some slides, and motivate their project's raison d'être. One example is here https://www.youtube.com/watch?v=_Q888b0VRx8&t=28s. Well done, capitan! But ...
Even though I am just here to code, I'd like to put an idea on the table: What if we come up with our own video? One that drops all that jibber jabber and just takes the cake? Something original, funny yet informative and catchy! Something that conveys the audience, that (even if one might get a bored feeling when looking into supercomputer land) life with Elastic is everything but boring and unsexy
Just an idea, the jibber jabber can be saved for some conference right? Maybe we could sign up for the next Devcon and arrive stuffed into multiple loads of busses wearing Elastic t-shirts (edit: aaaww, forgot that it would require us to do something with smart contracts, ... maybe I implement a smart contract blocker, if that's enough)!
When we take a look at other projects, we see a long history of videos where developers do some jibber jabber, show some slides, and motivate their project's raison d'être. One example is here https://www.youtube.com/watch?v=_Q888b0VRx8&t=28s. Well done, capitan! But ...
Even though I am just here to code, I'd like to put an idea on the table: What if we come up with our own video? One that drops all that jibber jabber and just takes the cake? Something original, funny yet informative and catchy! Something that conveys the audience, that (even if one might get a bored feeling when looking into supercomputer land) life with Elastic is everything but boring and unsexy
Just an idea, the jibber jabber can be saved for some conference right? Maybe we could sign up for the next Devcon and arrive stuffed into multiple loads of busses wearing Elastic t-shirts (edit: aaaww, forgot that it would require us to do something with smart contracts, ... maybe I implement a smart contract blocker, if that's enough)!
November 25, 2016, 02:12:40 PM
Short News: Behind the curtains, plans are being plotted to pull off a GPU miner ;-) One step closer to super-computer-market domination!
can't wait to share this great news to my fellows.
we have a growing community!
http://btc12.com/thread-378.htm
November 25, 2016, 01:54:13 PM
The possibilities are limitless really. Something needs to be done with idle mining power.
November 25, 2016, 01:53:14 PM
Lets just put in some fail safes to ensure it doesnt turn into SkyNet
So what? At last, world domination *laughs in binary*
This was one of the crazy ideas, that I had, though: Write an autonomous trading bot, that can learn and uses XEL to calculate its next trades, and whose main goal is to fuel its XEL needs (and maybe even its server space), all built inside a "black box", so that you can monitor it, but not access or manipulate its decisions.
November 25, 2016, 01:44:33 PM
Short News: Behind the curtains, plans are being plotted to pull off a GPU miner ;-) One step closer to super-computer-market domination!
can't wait to share this great news to my fellows.
we have a growing community!
http://btc12.com/thread-378.htm
November 25, 2016, 01:39:23 PM
Lets just put in some fail safes to ensure it doesnt turn into SkyNet
November 25, 2016, 01:30:28 PM
Short News: Behind the curtains, plans are being plotted to pull off a GPU miner ;-) One step closer to super-computer-market domination!
November 25, 2016, 01:27:25 PM
Also, @everyone that helped! Do not forget, you are "Elastic Core Developers" and "Authors" of the code:
If you want your names splattered all around the code, the UI and the Github changelogs, then please give me a short notice. If you do not want your BCT username linked to your name, just submit an Issue Ticket in the github an I will add you asap!
very nice, i guess me helping with testnet at the beginning makes me not qualified If you want your names splattered all around the code
, the UI and the Github changelogs, then please give me a short notice. If you do not want your BCT username linked to your name, just submit an Issue Ticket in the github an I will add you asap! amazing job guys!!!Well, I guess, I'm even less qualified than you
November 25, 2016, 10:30:33 AM
@coralreefer: agreed! I have still extended the error messages a bit so we have it easier in the future.
These are possible:
And of course a plain
if it's really a duplicate.
These are possible:
Code:
Proof of Work:
Duplicate unconfirmed transaction: work is already closed
Duplicate unconfirmed transaction: maximum pows per block reached
Duplicate unconfirmed transaction: work ran out of funds
Bounty Announcement:
Duplicate unconfirmed transaction: no more bounty announcement slots available
Bounty:
Duplicate unconfirmed transaction: work is already closed, you missed the reveal period
And of course a plain
Code:
Duplicate unconfirmed transaction
if it's really a duplicate.
EK, when you get a sec can you take a look to see if these messages are working correctly in the latest core. I get "Duplicate unconfirmed transaction" when I think I should have got "Duplicate unconfirmed transaction: no more bounty announcement slots available".
November 25, 2016, 09:52:02 AM
Also, @everyone that helped! Do not forget, you are "Elastic Core Developers" and "Authors" of the code:
If you want your names splattered all around the code, the UI and the Github changelogs, then please give me a short notice. If you do not want your BCT username linked to your name, just submit an Issue Ticket in the github an I will add you asap!
If you want your names splattered all around the code
, the UI and the Github changelogs, then please give me a short notice. If you do not want your BCT username linked to your name, just submit an Issue Ticket in the github an I will add you asap!is it possible to splatter "Chinese XEL Community: QQ Group 543181509"
lol, i did nothing, but i am ready to push this great project to more users.
Big whales coming from China are paying attention, EK you will be famous for xel
November 25, 2016, 09:39:26 AM
Also, @everyone that helped! Do not forget, you are "Elastic Core Developers" and "Authors" of the code:
If you want your names splattered all around the code, the UI and the Github changelogs, then please give me a short notice. If you do not want your BCT username linked to your name, just submit an Issue Ticket in the github an I will add you asap!
If you want your names splattered all around the code
, the UI and the Github changelogs, then please give me a short notice. If you do not want your BCT username linked to your name, just submit an Issue Ticket in the github an I will add you asap!is it possible to splatter "Chinese XEL Community: QQ Group 543181509"
lol, i did nothing, but i am ready to push this great project to more users.
November 25, 2016, 09:17:33 AM
Also, @everyone that helped! Do not forget, you are "Elastic Core Developers" and "Authors" of the code:
If you want your names splattered all around the code, the UI and the Github changelogs, then please give me a short notice. If you do not want your BCT username linked to your name, just submit an Issue Ticket in the github an I will add you asap!
very nice, i guess me helping with testnet at the beginning makes me not qualified If you want your names splattered all around the code
, the UI and the Github changelogs, then please give me a short notice. If you do not want your BCT username linked to your name, just submit an Issue Ticket in the github an I will add you asap! amazing job guys!!! November 25, 2016, 07:38:00 AM
Also, @everyone that helped! Do not forget, you are "Elastic Core Developers" and "Authors" of the code:
If you want your names splattered all around the code, the UI and the Github changelogs, then please give me a short notice. If you do not want your BCT username linked to your name, just submit an Issue Ticket in the github an I will add you asap!
If you want your names splattered all around the code
, the UI and the Github changelogs, then please give me a short notice. If you do not want your BCT username linked to your name, just submit an Issue Ticket in the github an I will add you asap! November 25, 2016, 07:27:20 AM
The chain is moving finally (without doing git pull) but will recompile right now.
Because I can't redeem xel maybe someone could send me some test-xel : XEL-XFMU-85XU-V4S3-EZZY2
Because I can't redeem xel maybe someone could send me some test-xel : XEL-XFMU-85XU-V4S3-EZZY2
Finally fixed your "could not verify transaction bytes" issue
Its in the git as of now! November 25, 2016, 06:23:56 AM
Fixed syncing issues on 0.7.2
November 25, 2016, 05:23:46 AM
In case the chain does not sync: keep calm ;-) I am right now fixing the connectivity issues!
November 25, 2016, 04:57:01 AM
I have added this estimation in the 0.7.2 version.
Please check if all works, and if the code both makes sense and is resistant to numerous attacks and failures!!
The push containing this change includes these commits:
https://github.com/OrdinaryDude/elastic-core/commit/1c8439bcc46cc12387afe5c7de1c7c2b86fd133f
https://github.com/OrdinaryDude/elastic-core/commit/20b3728cc8f7732a811145767488aa545d3ba723
https://github.com/OrdinaryDude/elastic-core/commit/1c8439bcc46cc12387afe5c7de1c7c2b86fd133f
Mining on one of my i7 4660HQ cores, the UI now somewhat correctly estimates my Gigaflop power (I am the only one mining):
Please check if all works, and if the code both makes sense and is resistant to numerous attacks and failures!!
The push containing this change includes these commits:
https://github.com/OrdinaryDude/elastic-core/commit/1c8439bcc46cc12387afe5c7de1c7c2b86fd133f
https://github.com/OrdinaryDude/elastic-core/commit/20b3728cc8f7732a811145767488aa545d3ba723
https://github.com/OrdinaryDude/elastic-core/commit/1c8439bcc46cc12387afe5c7de1c7c2b86fd133f
Mining on one of my i7 4660HQ cores, the UI now somewhat correctly estimates my Gigaflop power (I am the only one mining):
November 25, 2016, 03:07:57 AM
I am trying to measure the Elastic Network's performance in Gigaflops! Far from trivial, here are my thoughts.
What do you think?
How is the Gigaglop Estimation Performed?
Estimating the network's computation power is not a trivial task since many different architectures with a broad variety of hardware come together. So please keep in mind, that an accurate estimation is not possible at this point. However, we are using the following technique to roughly estimate the network's computation power from empirical values that we have collected on a reference computer:
Disclaimer: The estimated Gigaflops can be unprecise and differ significantly from the reality!
Now comes the magic:
What do you think?
How is the Gigaglop Estimation Performed?
Estimating the network's computation power is not a trivial task since many different architectures with a broad variety of hardware come together. So please keep in mind, that an accurate estimation is not possible at this point. However, we are using the following technique to roughly estimate the network's computation power from empirical values that we have collected on a reference computer:
Disclaimer: The estimated Gigaflops can be unprecise and differ significantly from the reality!
- We begin with a very simple work task, the simplest possible that contains just one verify statement with one expression
- We are using an Intel i7 4700HQ as the reference CPU, and measure (over a long period) how many POW packages we (on average) generate in each 360 second period on minimal difficulty. We are using a highly optimized C miner and assume that the C code optimization we achieve using GCC reflects the fastest possible way to run that work package on that CPU.
- We know that the i7 4700HQ performs at 3.34 Gigaflop/s per core. On one core, this CPU generates on average X POW per 360 second period on minimal difficulty
- The above values are hard coded into GigaflopEstimator.java, let's now look at what happens at the users' computers
- At the beginning the client measures how long it takes to evaluate the very simple program in the Elastic PL interpreter on the users' machine, and, every time the client sees a new work package, it measures how long it takes to evaluate it as well. It calculates a stretch-factor which indicates how much more it takes to evaluate other work packages in comparison to the simple work package. The thought is, if the strech factor of a new work package is for example x2 and we still generate the same amount of POW submissions for the lowest difficulty per 360s frame, we can assume that our computation power has doubled
- Now, the client constantly monitors all open works, their POW submission rates (of the total network) per 360s frame, and their difficulty. We only account for works that have received a POW in the last 3 blocks, to ignore works that are not being worked on due to whatever reason.
Now comes the magic:
- From the strech-facor for each work and the target (which itself can be seen as a scaling factor, since the target throttles linearly the POW rate in relation to the computational power) each client can derive the estimated POW rate per 360s that we would likely have if both the target would be minimal on all work packages and all works were as simple as they could be
- From the hard coded rate at which an i7 4770HQ can generate such POWs (minimal target and minimal complexity) [see point 3 above] we can now estimate how many cores an i7 4770HQ would have to have in order to generate the same amount of POWs per 360 second frame that we have seen in the network
- From the Gigaflop power of each core of the i7 4770HQ [again, point 3 above] we can estimate how many Gigaflops the entire Elastic network must have.
November 24, 2016, 07:39:38 PM
Something like this!
BUt i found a more serious issue in the miner.
It uses 100% CPU on all threads even if no work is live and it should be idle ;-)
BUt i found a more serious issue in the miner.
It uses 100% CPU on all threads even if no work is live and it should be idle ;-)
I'll take a look at this. On my system the threads go back to minimal usage, but with the recent changes, I may have broken something. Should be pretty easy to fix.
I noticed it when I launched the miner when there was work online and waited until the work was finished! I will try to reproduce this once again.
There is a difference when there is no work vs work, but none eligible to be mined (i.e. no bounties left). I would guess on your system with no work, it idles, but with non-eligible work, it's still doing something...that's what I may have broken when I redid all the i/o logic.
Here it's reproducible when I just start the miner up with no work:
EK, I've posted an updated miner. Let me know if this fixes the issue for you. I think it was caused during my i/o redesign by the removal of the 15 sec sleep when there is no work. I have incorporated a modified 15 sec sleep now.
Jump to: