Pages:
Author

Topic: Execoin: | First Open-Source Stealth Wallet Released! | Fast | ASIC-proof - page 53. (Read 281694 times)

sr. member
Activity: 313
Merit: 250
this coin is going places
full member
Activity: 147
Merit: 100
+400k. this guy'll be the top 1 holder for sure Shocked
newbie
Activity: 22
Merit: 0
OMG what a spike !!  Shocked

Edit : what a 2nd spike !!  Shocked  Shocked
full member
Activity: 219
Merit: 100
is it possible to merge-mine exe with both mon/plx like vtc on simplevert?
full member
Activity: 239
Merit: 103
I am happy to say I got the exechain to work.  I am not yet 100% sure why it wasn't working yet, but am planning to dig into it.  I was using the zen2pool version of p2pool and am now using donSchoe's version of it.  I started the chain on a fresh vm and then connected to it with my other systems and it worked without a hitch (first vm started with persistant set to false and then added the others with true (not sure if this matters, but that is what I did)).

The code I used

Code:
execoin2=math.Object(
        PARENT=networks.nets['execoin'],
        SHARE_PERIOD=22, # seconds
        CHAIN_LENGTH=24*60*60//10, # shares
        REAL_CHAIN_LENGTH=24*60*60//10, # shares
        TARGET_LOOKBEHIND=200, # shares
        SPREAD=55, # blocks
        IDENTIFIER='657865636fe89f61'.decode('hex'),
        PREFIX='656578656398ed71'.decode('hex'),
        P2P_PORT=25000,
        MIN_TARGET=4,
        MAX_TARGET=2**256//2**20 - 1,
        PERSIST=True,
        WORKER_PORT=9173,
        BOOTSTRAP_ADDRS='216.249.119.195 216.249.119.194 216.249.119.112'.split(' '),
        ANNOUNCE_CHANNEL='#p2pool-exe2',
        VERSION_CHECK=lambda v: True,
    ),

I will report back later on how the results fair after I've had some more time to test it.  Your welcome to test it for your selves to see if the longer block time works better for your gpu's.  You can connect to any of my nodes (current bootstrap_addrs's) or make your own.

What do you want to improve with your changes to the Share Period?

Just changing it to 22 Seconds Sharetime will make things work worse. Execoin Blocktime is 60 Seconds!
Dont take this personal but according to your past questions you seem to not really have a clue what your doing there.
So better don't change a working system.

If you want to improve Stales there are other things to do and these are mostly on the miners side. But keep in mind that with p2pool Stales are always higher that any traditional pool.

I did it partially for the learning experience and am experimenting with how it plays with my gpu's.  I changed the port so it shouldn't affect the current net.  One of my gpu's has issues with stales shares with the fast block time and, since the difficulty is low enough for me to solo mine, I decided that this was an oppertune time to try it out.  Nobody is obliged to use those setting unless they want to or feel like it might be worth trying.

Thats perfectly fine. More People interested in P2Pool is always a good thing  Grin

There are just some rules for the Values of P2Pool that have to match the Coin Specifications.

If you set the Sharetime to 22 Secs Miners will only have the chance to submit 2 Shares in the whole P2Pool Network until the next EXE Block is found. This works fine with 10-20 Mh/s.
But the P2Pool wont scale well since this slow Sharetime will drive Sharedifficulty very high as Poolspeed increases. This will be a big Problem for smaller Miners since they get very inconsistent Payments.
This was one issue VTC P2Pool was facing before some changes where made. Even now as a small miner its better to not use the main VTC P2Pool.

member
Activity: 118
Merit: 100
Please can someone tell me if p2pool are more profitable than mining pools, and exactly why? I'm thinking of switching to p2pool but I'm a little scared ...
sr. member
Activity: 336
Merit: 250
There is a day to be born, and another to die
Quote
Important Note : we should send MintPal coin suggestion via submit ticket like we did with AsiaCoin many users submitted ticket and in 4 days they added Asiacoin !! everyone should submit ticket link is below

Mintpal Coin suggestion -> https://support.mintpal.com/index.php?module=tickets&sec=submit.step1


2nd -> Every Single user who use Twitter please tweet them to add Execoin on Exchange, The more you tweet then we have more chance to get soon on exchange coz they actually now check how many users interested in this coin !! Cheers !!

Mintpal Twitter -> https://twitter.com/MintPalExchange

Tweet Example : @MintPalExchange please add @execoin_dev to your exchange ( include some text from your side ) .

@Dev hope this work !! Tip will be good  Cheesy Cheesy Cheesy
sr. member
Activity: 308
Merit: 250

Execoin Development Fund

Donations will be greatly appreciated:

EXE: EZF3TXHFEwK58cjESPewcPHk9pZ5M6nDBF  
BTC: 1D9x2Jt3uJUxptZZLha1UvzAeHR7tn9zpS

Just donated 200 EXE  Wink

txid b6468a4535e5e209ddcafe2a583e637a05d871974a2d2ad1608a7253925287cb
full member
Activity: 158
Merit: 100
I am happy to say I got the exechain to work.  I am not yet 100% sure why it wasn't working yet, but am planning to dig into it.  I was using the zen2pool version of p2pool and am now using donSchoe's version of it.  I started the chain on a fresh vm and then connected to it with my other systems and it worked without a hitch (first vm started with persistant set to false and then added the others with true (not sure if this matters, but that is what I did)).

The code I used

Code:
execoin2=math.Object(
        PARENT=networks.nets['execoin'],
        SHARE_PERIOD=22, # seconds
        CHAIN_LENGTH=24*60*60//10, # shares
        REAL_CHAIN_LENGTH=24*60*60//10, # shares
        TARGET_LOOKBEHIND=200, # shares
        SPREAD=55, # blocks
        IDENTIFIER='657865636fe89f61'.decode('hex'),
        PREFIX='656578656398ed71'.decode('hex'),
        P2P_PORT=25000,
        MIN_TARGET=4,
        MAX_TARGET=2**256//2**20 - 1,
        PERSIST=True,
        WORKER_PORT=9173,
        BOOTSTRAP_ADDRS='216.249.119.195 216.249.119.194 216.249.119.112'.split(' '),
        ANNOUNCE_CHANNEL='#p2pool-exe2',
        VERSION_CHECK=lambda v: True,
    ),

I will report back later on how the results fair after I've had some more time to test it.  Your welcome to test it for your selves to see if the longer block time works better for your gpu's.  You can connect to any of my nodes (current bootstrap_addrs's) or make your own.

What do you want to improve with your changes to the Share Period?

Just changing it to 22 Seconds Sharetime will make things work worse. Execoin Blocktime is 60 Seconds!
Dont take this personal but according to your past questions you seem to not really have a clue what your doing there.
So better don't change a working system.

If you want to improve Stales there are other things to do and these are mostly on the miners side. But keep in mind that with p2pool Stales are always higher that any traditional pool.

I did it partially for the learning experience and am experimenting with how it plays with my gpu's.  I changed the port so it shouldn't affect the current net.  One of my gpu's has issues with stales shares with the fast block time and, since the difficulty is low enough for me to solo mine, I decided that this was an oppertune time to try it out.  Nobody is obliged to use those setting unless they want to or feel like it might be worth trying.
sr. member
Activity: 308
Merit: 250
I contacted 'sameev29' that who can make multipool,he said could make a multipool for Execoin.
Devs look personal message please.


That would be awesome!!
sr. member
Activity: 336
Merit: 250
There is a day to be born, and another to die
I contacted 'sameev29' that who can make multipool,he said could make a multipool for Execoin.
Devs look personal message please.
full member
Activity: 239
Merit: 103
I am happy to say I got the exechain to work.  I am not yet 100% sure why it wasn't working yet, but am planning to dig into it.  I was using the zen2pool version of p2pool and am now using donSchoe's version of it.  I started the chain on a fresh vm and then connected to it with my other systems and it worked without a hitch (first vm started with persistant set to false and then added the others with true (not sure if this matters, but that is what I did)).

The code I used

Code:
execoin2=math.Object(
        PARENT=networks.nets['execoin'],
        SHARE_PERIOD=22, # seconds
        CHAIN_LENGTH=24*60*60//10, # shares
        REAL_CHAIN_LENGTH=24*60*60//10, # shares
        TARGET_LOOKBEHIND=200, # shares
        SPREAD=55, # blocks
        IDENTIFIER='657865636fe89f61'.decode('hex'),
        PREFIX='656578656398ed71'.decode('hex'),
        P2P_PORT=25000,
        MIN_TARGET=4,
        MAX_TARGET=2**256//2**20 - 1,
        PERSIST=True,
        WORKER_PORT=9173,
        BOOTSTRAP_ADDRS='216.249.119.195 216.249.119.194 216.249.119.112'.split(' '),
        ANNOUNCE_CHANNEL='#p2pool-exe2',
        VERSION_CHECK=lambda v: True,
    ),

I will report back later on how the results fair after I've had some more time to test it.  Your welcome to test it for your selves to see if the longer block time works better for your gpu's.  You can connect to any of my nodes (current bootstrap_addrs's) or make your own.

What do you want to improve with your changes to the Share Period?

Just changing it to 22 Seconds Sharetime will make things work worse. Execoin Blocktime is 60 Seconds!
Dont take this personal but according to your past questions you seem to not really have a clue what your doing there.
So better don't change a working system.

If you want to improve Stales there are other things to do and these are mostly on the miners side. But keep in mind that with p2pool Stales are always higher that any traditional pool.
sr. member
Activity: 308
Merit: 250
Every time I buy some EXE on Poloniex that pushes the price up, within 5-10 minutes a sell order is placed that pushes the price back down. If I had more BTC I could sit there and do that all day long.  Huh
sr. member
Activity: 336
Merit: 250
There is a day to be born, and another to die
Does devs not intend to add more features?Hope devs to be like DRK devs!
full member
Activity: 158
Merit: 100
I am happy to say I got the exechain to work.  I am not yet 100% sure why it wasn't working yet, but am planning to dig into it.  I was using the zen2pool version of p2pool and am now using donSchoe's version of it.  I started the chain on a fresh vm and then connected to it with my other systems and it worked without a hitch (first vm started with persistant set to false and then added the others with true (not sure if this matters, but that is what I did)).

The code I used

Code:
execoin2=math.Object(
        PARENT=networks.nets['execoin'],
        SHARE_PERIOD=22, # seconds
        CHAIN_LENGTH=24*60*60//10, # shares
        REAL_CHAIN_LENGTH=24*60*60//10, # shares
        TARGET_LOOKBEHIND=200, # shares
        SPREAD=55, # blocks
        IDENTIFIER='657865636fe89f61'.decode('hex'),
        PREFIX='656578656398ed71'.decode('hex'),
        P2P_PORT=25000,
        MIN_TARGET=4,
        MAX_TARGET=2**256//2**20 - 1,
        PERSIST=True,
        WORKER_PORT=9173,
        BOOTSTRAP_ADDRS='216.249.119.195 216.249.119.194 216.249.119.112'.split(' '),
        ANNOUNCE_CHANNEL='#p2pool-exe2',
        VERSION_CHECK=lambda v: True,
    ),

I will report back later on how the results fair after I've had some more time to test it.  Your welcome to test it for your selves to see if the longer block time works better for your gpu's.  You can connect to any of my nodes (current bootstrap_addrs's) or make your own.
full member
Activity: 158
Merit: 100

If it tries to download shares its still somehow connected to the main EXE P2Pool.

You could try and delete all data in the data/execoin directory.

I removed everything inside the data directory and it is still giving me the same errors...

Here is the current iteration of the code I am working with

Code:
execoin2=math.Object(
        PARENT=networks.nets['execoin'],
        SHARE_PERIOD=22, # seconds
        CHAIN_LENGTH=24*60*60//10, # shares
        REAL_CHAIN_LENGTH=24*60*60//10, # shares
        TARGET_LOOKBEHIND=200, # shares
        SPREAD=55, # blocks
        IDENTIFIER='657865636fe89f61'.decode('hex'),
        PREFIX='656578656398ed71'.decode('hex'),
        P2P_PORT=25000,
        MIN_TARGET=4,
        MAX_TARGET=2**256//2**20 - 1,
        PERSIST=True,
        WORKER_PORT=9173,
        BOOTSTRAP_ADDRS='216.249.119.194'.split(' '),
        ANNOUNCE_CHANNEL='#p2pool-exe2',
        VERSION_CHECK=lambda v: True,
    ),

Do you think I need to edit bitcoin/networks.py as well?

The errors I am getting are:

Quote
P2Pool: 0 shares in chain (0 verified/0 total) Peers: 1 (0 incoming)
2014-05-12 22:40:26.502038  Local: 0H/s in last 0.0 seconds Local dead on arrival: Huh Expected time to share: Huh
> Unhandled Error
> Traceback (most recent call last):
>   File "/opt/zen2pool2/zen2pool/p2pool/main.py", line 578, in run
>     reactor.run()
>   File "/usr/lib/python2.7/dist-packages/twisted/internet/base.py", line 1169, in run
>     self.mainLoop()
>   File "/usr/lib/python2.7/dist-packages/twisted/internet/base.py", line 1178, in mainLoop
>     self.runUntilCurrent()
>   File "/usr/lib/python2.7/dist-packages/twisted/internet/base.py", line 800, in runUntilCurrent
>     call.func(*call.args, **call.kw)
> --- --- >   File "/opt/zen2pool2/zen2pool/p2pool/bitcoin/stratum.py", line 38, in _send_work
>     x, got_response = self.wb.get_work(*self.wb.preprocess_request('' if self.username is None else self.username))
>   File "/opt/zen2pool2/zen2pool/p2pool/bitcoin/worker_interface.py", line 129, in get_work
>     x, handler = self._inner.get_work(*args)
>   File "/opt/zen2pool2/zen2pool/p2pool/work.py", line 207, in get_work
>     raise jsonrpc.Error_for_code(-12345)(u'p2pool is downloading shares')
> p2pool.util.jsonrpc.NarrowError: -12345 p2pool is downloading shares
2014-05-12 22:40:32.686568 Skipping from block 6c4424bdd527755bcb33d98ba8619e44a1437224814026f2d9fa091d0a3d8d4a to block e94b37e7efcf8ab49f319e062efa7c304211818e034b25d77b34817619bb79b9!
2014-05-12 22:40:32.796935 Got new merged mining work!
sr. member
Activity: 308
Merit: 250

Execoin website has been updated!

- Added "where to spend?" section with list of stores and services accepting execoins, as well as FIAT exchange.
- Website has been optimized for low screen resolutions; fixed overlapping of navigation menu with logo image.


Looks good   Smiley

The new "Where to spend?" section of the website adds a lot of helpful information all in one place--online stores that accept EXE, fiat exchange, crypto exchanges that list EXE and while the donation addresses to the Execoin fund seem a little out of place, I'm glad they're listed on the website. We must support the development of this coin if we want it to be successful, so please donate and help spread the word!
full member
Activity: 204
Merit: 100

Execoin website has been updated!

- Added "where to spend?" section with list of stores and services accepting execoins, as well as FIAT exchange.
- Website has been optimized for low screen resolutions; fixed overlapping of navigation menu with logo image.




full member
Activity: 239
Merit: 103
Here is what I have for another network, It does not work at the moment.

Quote

execoin2=math.Object(
        PARENT=networks.nets['execoin'],
        SHARE_PERIOD=22, # seconds
        CHAIN_LENGTH=24*60*60//10, # shares
        REAL_CHAIN_LENGTH=24*60*60//10, # shares
        TARGET_LOOKBEHIND=200, # shares
        SPREAD=55, # blocks
        IDENTIFIER='657865636f696e65'.decode('hex'),
        PREFIX='65657865636f696e'.decode('hex'),
        P2P_PORT=25000,
        MIN_TARGET=4,
        MAX_TARGET=2**256//2**20 - 1,
        PERSIST=True,
        WORKER_PORT=9173,
        BOOTSTRAP_ADDRS='216.249.119.195'.split(' '),
        ANNOUNCE_CHANNEL='#p2pool-exe2',
        VERSION_CHECK=lambda v: True,
    ),

I changed the P2P_port to 25000 (from 9986) the share_period to 22 (from 10) and the spread to 55 (from 50) and the announce channel to p2pool-exe2 (from p2pool-exe).  I did not change the Identifier and Prefix (not sure what to change them to), although I do believe they may need to be changed.  I am having issues establishing a connection between two nodes (two vm's).  Any ideas?



Change the last 6 digits of IDENTIFIER and PREFIX randomly with hex values between 0-9 and a-f.

Then change the BOOTSTRAP_ADDRS to the IP Address one of your VMs has.

Still doesn't seem to work, gets stuck trying to download shares (both systems display a that they are connected to a peer in the console but the gui has the connections as blank)...

If it tries to download shares its still somehow connected to the main EXE P2Pool.

You could try and delete all data in the data/execoin directory.
newbie
Activity: 20
Merit: 0
 think EXEcoin can last up to the best price
Pages:
Jump to: