Bitcoin Forum
November 12, 2024, 10:50:50 PM *
News: Check out the artwork 1Dq created to commemorate this forum's 15th anniversary
 
   Home   Help Search Login Register More  
Pages: « 1 ... 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 [83] 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 ... 345 »
  Print  
Author Topic: [ANN][XEL] Elastic Project - The Decentralized Supercomputer  (Read 450515 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.
tomkat
Hero Member
*****
Offline Offline

Activity: 1022
Merit: 507


View Profile
September 07, 2016, 03:37:02 PM
 #1641

If submitting work cost something, then the submission cost should be enough to prevent flooding, no...?

Submitting work costs, but submitting a POW solutions or a bounty submission is a zero fee transaction, so even accounts with no XEL can start solving work right away.
I mean we could require a fee and then refund it once the tx confirms, but that would make it more difficult for new users to start earning XEL.

I will think a moment about this. Maybe we should work with the NXT devs here; I am almost sure that they suffer from the same issue. The difference is that their TX cost something, but as malicious TX will never confirm and eventually will be rolled back, attacking NXT does not cost the attacker anything after all. I am pretty sure you could DOS the NXT chain easily. We need a solution here.

Well, not sure if it can be solved as it would be difficult to determine if a flood of submissions is made up of fake numbers, or it's a series of real values calculated by a super fast PoW miner.
yusyus
Hero Member
*****
Offline Offline

Activity: 495
Merit: 500


View Profile
September 07, 2016, 07:43:07 PM
 #1642

How and when I can receive my XEL?
Does wallet ready?
trader19
Legendary
*
Offline Offline

Activity: 1232
Merit: 1001



View Profile WWW
September 07, 2016, 07:46:41 PM
 #1643

How and when I can receive my XEL?
Does wallet ready?
join us on testnet and help us find bugs, as much we all help sooner we get to mainnet release and party timeee

Join the Elastic revolution!  Elastic - The Decentralized Supercomputer
ELASTIC WEBSITE | NEW ANNOUNCEMENT THREAD | ELASTIC SLACK | ELASTIC FORUM
unvoid
Hero Member
*****
Offline Offline

Activity: 535
Merit: 500



View Profile
September 08, 2016, 08:01:39 AM
 #1644

1. Blacklist problem: Can we disallow to process jobs that are less than 5 blocks old? This way every node will know about job before any submission will hit the network.
2. Can we separate workers for the ones that have XEL and dosen't have? Workers with XEL can submit bounty with fee that will be returned later. Workers without XEL:

Can't submit more than X bounty, and in UI they have a notice about it "Get some XEL to be able to submit more than X solutions for one job".

Code:
if ( IP_ADDRESS && EMPTY_XEL_ADDRESS && submittedMoreThanXBounty) { // where X is a number of submission we choose as safe

   rejectSubmission;
   addThisIncidentToTheList;

   if(thereWasMoreIncidentsThanY) {
     
      blacklistNode;
   }

}

Just a thoughts. Any other suggestions?

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

Activity: 535
Merit: 500



View Profile
September 08, 2016, 08:05:53 AM
 #1645

If you want to try XEL:

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.

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

Activity: 535
Merit: 500



View Profile
September 08, 2016, 08:13:30 AM
 #1646

If you want to try out a miner:

1. Download it from: https://github.com/OrdinaryDude/elastic-miner
2. ./compile.sh
3. ./run.sh
4. Give it your passphrase (after you hit a key make sure visible XEL address is yours)
5. Give it a XEL running daemon IP address (default localhost)
6. Hit enter and submit work to the network in your XEL client UI as shown here https://player.vimeo.com/video/178616474?quality=1080p. If someone else will submit work to the network your miner will automatically start working on it.
7. Example work are here https://github.com/OrdinaryDude/elastic-reference-client/tree/master/elasticpl_examples. no_bounties_found.epl will not found any bounty! Be warned that this is debug job that will just expire after 250 blocks without any submissions.

Suggestions:

run miner with lower cpu priority for optimal experience. Especialy if you running miner on the same machine that you running XEL node.

i. e.

Code:
screen nice -n 20 ./run.sh
20 is lowest possible priority in most linux env.

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

Activity: 1022
Merit: 507


View Profile
September 08, 2016, 08:14:03 AM
 #1647

1. Blacklist problem: Can we disallow to process jobs that are less than 5 blocks old? This way every node will know about job before any submission will hit the network.
2. Can we separate workers for the ones that have XEL and dosen't have? Workers with XEL can submit bounty with fee that will be returned later. Workers without XEL:

Can't submit more than X bounty, and in UI they have a notice about it "Get some XEL to be able to submit more than X solutions for one job".

Code:
if ( IP_ADDRESS && EMPTY_XEL_ADDRESS && submittedMoreThanXBounty) { // where X is a number of submission we choose as safe

   rejectSubmission;
   addThisIncidentToTheList;

   if(thereWasMoreIncidentsThanY) {
      
      blacklistNode;
   }

}

Just a thoughts. Any other suggestions?


Perhaps, as a general rule, in order to become worker, one would need to have a collateral from which the submission fees would be financed.
Then once the work is completed, the fees would be paid back to the collateral account.
Similar solution is used in XEM for instance where you need to place 3M XEM to become supernode, or need to have at least 10K vested XEM balance to start forging.
This could be an incentive for longer commitment, and more involvement in XEL, and perhaps stabilize XEL price (slightly)
hagie
Hero Member
*****
Offline Offline

Activity: 792
Merit: 501



View Profile
September 08, 2016, 08:25:40 AM
 #1648

If you want to try out a miner:

1. Download it from: https://github.com/OrdinaryDude/elastic-miner
2. ./compile.sh
3. ./run.sh
4. Give it your passphrase (after you hit a key make sure visible XEL address is yours)
5. Give it a XEL running daemon IP address (default localhost)
6. Hit enter and submit work to the network in your XEL client UI as shown here https://player.vimeo.com/video/178616474?quality=1080p. If someone else will submit work to the network your miner will automatically start working on it.
7. Example work are here https://github.com/OrdinaryDude/elastic-reference-client/tree/master/elasticpl_examples. no_bounties_found.epl will not found any bounty! Be warned that this is debug job that will just expire after 250 blocks without any submissions.

Suggestions:

run miner with lower cpu priority for optimal experience. Especialy if you running miner on the same machine that you running XEL node.

i. e.

Code:
screen nice -n 20 ./run.sh
20 is lowest possible priority in most linux env.

Hi,

so forging and mining are different ?

Mining = Work on Computing jobs
Forging = Keep the chain running by producing blocks

right ?

Regards
unvoid
Hero Member
*****
Offline Offline

Activity: 535
Merit: 500



View Profile
September 08, 2016, 08:38:44 AM
 #1649

Right.

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

Activity: 792
Merit: 501



View Profile
September 08, 2016, 08:48:29 AM
 #1650

Right.

Thanks for the clarification. Anyway - I can't put work on the network I get the "Could not verify signature (server side)." Error when creating a Job or register my Account. Any Hint how to solve this ?

Regards
unvoid
Hero Member
*****
Offline Offline

Activity: 535
Merit: 500



View Profile
September 08, 2016, 08:52:51 AM
 #1651

I will think a moment about this. Maybe we should work with the NXT devs here; I am almost sure that they suffer from the same issue. The difference is that their TX cost something, but as malicious TX will never confirm and eventually will be rolled back, attacking NXT does not cost the attacker anything after all. I am pretty sure you could DOS the NXT chain easily. We need a solution here.

Would be awesome if any dev from NXT could join us for a moment or two. I've seen that CfB is quite active on BCT. Maybe he could be helpful?

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

Activity: 535
Merit: 500



View Profile
September 08, 2016, 09:09:08 AM
 #1652

Right.

Thanks for the clarification. Anyway - I can't put work on the network I get the "Could not verify signature (server side)." Error when creating a Job or register my Account. Any Hint how to solve this ?

Regards

I've problem with reproducing this. In NRS.verifyAndSignTransactionBytes function lot of conditions returns false. Maybe irrelevant question but do you have proper date set on your computer?

Is your node public? Can I login to it?

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

Activity: 792
Merit: 501



View Profile
September 08, 2016, 09:15:37 AM
 #1653

Right.

Thanks for the clarification. Anyway - I can't put work on the network I get the "Could not verify signature (server side)." Error when creating a Job or register my Account. Any Hint how to solve this ?

Regards

I've problem with reproducing this. In NRS.verifyAndSignTransactionBytes function lot of conditions returns false. Maybe irrelevant question but do you have proper date set on your computer?

Is your node public? Can I login to it?

Yes the date is correct BUT it's shown wrong in the GUI

Code:
root@vmd14147:~# su - elastic
elastic@vmd14147:~$ date
Thu Sep  8 11:15:52 CEST 2016

And yes - it's the https://elastic.cryptnodes.site

Regards

unvoid
Hero Member
*****
Offline Offline

Activity: 535
Merit: 500



View Profile
September 08, 2016, 09:16:11 AM
 #1654

Is your node up to date? I've seen on the peer list that not all nodes updated latest @EK changes.

Stop your node, go to elastic directory and:

Code:
git pull origin master
./compile.sh
screen ./run.sh

I logged into your node. And as I said it's old version. Update and try again.

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

Activity: 535
Merit: 500



View Profile
September 08, 2016, 09:23:39 AM
Last edit: September 08, 2016, 09:39:52 AM by unvoid
 #1655

And please remember to del your blockchain before start. It's always good to delete blockchain after update in testnet.

Code:
rm -rf nxt_test_db/

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

Activity: 535
Merit: 500



View Profile
September 08, 2016, 09:29:51 AM
Last edit: September 08, 2016, 09:51:29 AM by unvoid
 #1656

If you want to try XEL:

Download testnet client https://github.com/OrdinaryDude/elastic-reference-client.
Best if you download it trough git for future easy updates. Install git on your machine and:

git clone https://github.com/OrdinaryDude/elastic-reference-client.git

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.



If you want to try out a miner:

1. Download it from: https://github.com/OrdinaryDude/elastic-miner
Best if you download it trough git for future easy updates. Install git on your machine and:

git clone https://github.com/OrdinaryDude/elastic-miner.git

2. ./compile.sh
3. ./run.sh
4. Give it your passphrase (after you hit a key make sure visible XEL address is yours)
5. Give it a XEL running daemon IP address (default localhost)
6. Hit enter and submit work to the network in your XEL client UI as shown here https://player.vimeo.com/video/178616474?quality=1080p. If someone else will submit work to the network your miner will automatically start working on it.
7. Example work are here https://github.com/OrdinaryDude/elastic-reference-client/tree/master/elasticpl_examples. no_bounties_found.epl will not found any bounty! Be warned that this is debug job that will just expire after 250 blocks without any submissions.

Suggestions:

run miner with lower cpu priority for optimal experience. Especialy if you running miner on the same machine that you running XEL node.

i. e.

Code:
screen nice -n 20 ./run.sh
20 is lowest possible priority in most linux env.



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



If you want to update miner to the newest version:

Stop your miner (CTRL + C)
Go to main directory of miner and:
Code:
git pull origin master
./compile.sh
screen nice -n 20 ./run.sh

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

Activity: 792
Merit: 501



View Profile
September 08, 2016, 09:45:16 AM
 #1657

And please remember to del your blockchain before start. It's always good to delete blockchain after update in testnet.

Code:
rm -rf nxt_test_db/

Updated to latest git. Signature problem when register account sill present.

You may try and log in.

regards
unvoid
Hero Member
*****
Offline Offline

Activity: 535
Merit: 500



View Profile
September 08, 2016, 10:06:05 AM
 #1658

And please remember to del your blockchain before start. It's always good to delete blockchain after update in testnet.

Code:
rm -rf nxt_test_db/

Updated to latest git. Signature problem when register account sill present.

You may try and log in.

regards

Your problem lays here:
nrs.server.js line 511:
Code:
if (transaction.recipient !== data.recipient) {
if (data.recipient == "5177795918244458805" && transaction.recipient == "0") {
//ok
} else {
return false;
}
}

I'll try to look at it after my work.

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

Activity: 1946
Merit: 1019



View Profile
September 08, 2016, 11:38:05 AM
 #1659


Node is updated and back on the right fork, anyone who needs some XEL give a shout.
Evil-Knievel
Legendary
*
Offline Offline

Activity: 1260
Merit: 1168



View Profile
September 08, 2016, 12:13:37 PM
 #1660

From now on I have no daytime job anymore, I will be working on Elastic full time until everything is up and running!
Today's agenda: Elastic was forked off NXT 1.4.5 I think. I will consider moving to the latest blockchain reorganization methodology from 1.9.2! I guess they added a few stability tweaks that should increase robustness. I will work in a different branch and merge it in once it's ready.
Pages: « 1 ... 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 [83] 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 ... 345 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!