Bitcoin Forum
June 20, 2024, 06:07:12 PM *
News: Voting for pizza day contest
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 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 »
821  Alternate cryptocurrencies / Mining (Altcoins) / Re: P2Pool Detailed Settings for Altcoins on: February 10, 2014, 02:26:44 AM
p2pool/networks.py

Unlike p2pool/bitcoin/networks.py some of the values here may be subjective and not clearly defined.
I will add my own personal comments to each setting. Please feel free to add your own or discuss opposing viewpoints.


For reference here is the section of the code for litecoin:
Code:
    litecoin=math.Object(
        PARENT=networks.nets['litecoin'],
        SHARE_PERIOD=15, # seconds
        CHAIN_LENGTH=24*60*60//10, # shares
        REAL_CHAIN_LENGTH=24*60*60//10, # shares
        TARGET_LOOKBEHIND=200, # shares
        SPREAD=3, # blocks
        IDENTIFIER='e037d5b8c6923410'.decode('hex'),
        PREFIX='7208c1a53ef629b0'.decode('hex'),
        P2P_PORT=9338,
        MIN_TARGET=0,
        MAX_TARGET=2**256//2**20 - 1,
        PERSIST=True,
        WORKER_PORT=9327,
        BOOTSTRAP_ADDRS='forre.st vps.forre.st liteco.in 95.211.21.103 37.229.117.57 66.228.48.21 180.169.60.179 112.84.181.102 74.214.62.115 209.141.46.154 78.27.191.182 66.187.70.88 88.190.223.96 78.47.242.59 158.182.39.43 180.177.114.80 216.230.232.35 94.231.56.87 62.38.194.17 82.67.167.12 183.129.157.220 71.19.240.182 216.177.81.88 109.106.0.130 113.10.168.210 218.22.102.12 85.69.35.7:54396 201.52.162.167 95.66.173.110:8331 109.65.171.93 95.243.237.90 208.68.17.67 87.103.197.163 101.1.25.211 144.76.17.34 209.99.52.72 198.23.245.250 46.151.21.226 66.43.209.193 59.127.188.231 178.194.42.169 85.10.35.90 110.175.53.212 98.232.129.196 116.228.192.46 94.251.42.75 195.216.115.94 24.49.138.81 61.158.7.36 213.168.187.27 37.59.10.166 72.44.88.49 98.221.44.200 178.19.104.251 87.198.219.221 85.237.59.130:9310 218.16.251.86 151.236.11.119 94.23.215.27 60.190.203.228 176.31.208.222 46.163.105.201 198.84.186.74 199.175.50.102 188.142.102.15 202.191.108.46 125.65.108.19 15.185.107.232 108.161.131.248 188.116.33.39 78.142.148.62 69.42.217.130 213.110.14.23 185.10.51.18 74.71.113.207 77.89.41.253 69.171.153.219 58.210.42.10 174.107.165.198 50.53.105.6 116.213.73.50 83.150.90.211 210.28.136.11 86.58.41.122 70.63.34.88 78.155.217.76 68.193.128.182 198.199.73.40 193.6.148.18 188.177.188.189 83.109.6.82 204.10.105.113 64.91.214.180 46.4.74.44 98.234.11.149 71.189.207.226'.split(' '),
        ANNOUNCE_CHANNEL='#p2pool-ltc',
        VERSION_CHECK=lambda v: True,
        VERSION_WARNING=lambda v: 'Upgrade Litecoin to >=0.8.5.1!' if v < 80501 else None,
    ),


For now here are some of my notes (work in progress):

SHARE_PERIOD
SHARE_PERIOD sets a target time for how often to provide a share. It will regulating the difficulty to try to hit that target time taking into account the setting in TARGET_LOOKBEHIND.
A lower number will have the effect of a lower share difficulty but also result in a larger share chain depending on the value in CHAIN_LENGTH. It may also cause additional orphans in the p2pool share chain as too low a difficulty will mean multiple miners will find shares at the same time. Not necessarily a bad thing as your all working on finding the same block but the winning finder will get the credit for the share.

Comment
I have seen people say a good rule of thumb is setting this to 1/5 of the altcoin block period. Too high a number will provide a higher diff share favoring higher hash rate miners. Too low a number increases resources (traffic, memory, storage) and orphans from competing miners finding the same shares. I believe setting this to 10 for most altcoins with block times of between 0.5 - 2 minutes is a good compromise.


CHAIN_LENGTH
CHAIN_LENGTH is the number of shares p2pool keeps before discarding them. It needs to be larger than or equal to REAL_CHAIN_LENGTH (it is normally equal to). One reason it increase this would be to show more data in the recent blocks found list.

Example: 24*60*60//10 = 1 day of shares. 7*24*60*60//10 = 7 days of shares. [verification needed]

REAL_CHAIN_LENGTH

REAL_CHAIN_LENGTH sets the total number of previously found shares to include in the payout when a block is found. A longer chain provides a larger amount of time to find a share (get paid for work).
It also contributes to how long you need mine to reach your "full" payout amount.

Comment
24*60*60//10 is calculated as follows:
(24*60*60)/10 = 8,640 shares are paid when a block is found.

Take the value in SHARE_PERIOD and multiply by the number of shares to find how many seconds a share is valid for.
For example:

8,640 shares will be paid with a share expected to be found every 10 seconds
8,640 * 10 = 86,400 seconds
86,400 / 60 = 1,440 minutes
1,440 / 60 = 24 hours
24 / 24 = 1 days

I have tried various REAL_CHAIN_LENGTH settings but have settled on 24*60*60//10 for the following reasons:
Allows a 24 hours period of time for finding of a share and for those shares to be valid based on having a share period of 10 seconds.
  • Allows smaller miners time to find a share within 24 hours
  • Amount of time to full payout increased but so does the time you continue to receive payment after you stop mining
  • Takes longer to ramp up to your full payout amount but you continue to get paid for about the same amount of time after you stop mining. With a  CHAIN_LENGTH setting of 24*60*60//10 I would say most miners reach their full payout between 6-8 hours and continue to receive a payout for about the same amount of time after they stop mining (depending on their hashrate and the setting in spread).



TARGET_LOOKBEHIND
Determines the number of shares counted for difficulty regulation.
Used to determine share difficulty based on the hash rate of p2pool (not individual nodes).

Comment
Some people set this really low but I recommend it be kept at 200 as it will modify the share diff based on the previous 200 shares rather quickly. I think they believe it will take TARGET_LOOKBEHIND*SHARE_PERIOD='time it takes to adjust' but I feel it actually uses the last 200 shares and adjust based on the average. Setting too low a number does not give it a large enough number of shares to determine the proper value and adjust smoothly.
With large miners coming and going the difficulty adjustment takes too long with 200 shares on smaller p2pool networks. On larger p2pool networks this is not noticeable but I have resulted to setting this to 20 to accommodate large miners coming and going.

SPREAD
SPREAD determines how many blocks (max) to pay if a miner finds at lease one share.
Does not go beyond the CHAIN_LENGTH/REAL_CHAIN_LENGTH setting.

Comment
600/[block time]=x
x*3=spread

Quote
bitcoin      SPREAD=3      block every 600 seconds         Baseline
litecoin     SPREAD=12     block every 150 seconds        600/150=4       4x3=12
bbqcoin      SPREAD=30     block every 60 seconds         600/60=10       10x3=30
casinocoin   SPREAD=60     block every 30 seconds         600/30=20       20x3=60
digitalcoin  SPREAD=90     block every 20 seconds         600/20=30       30x3=90  (old spec)
digitalcoin  SPREAD=45     block every 40 seconds         600/40=15       15x3=45  (new spec)
worldcoin    SPREAD=120    block every 15 seconds         600/15=40       40x3=120 (old spec)
worldcoin    SPREAD=60     block every 30 seconds         600/30=20       20x3=60  (new spec)
anoncoin     SPREAD=10     block every 205 seconds        600/205=2.926829268292683   2.926829268292683x3=8.780487804878049
globalcoin   SPREAD=45     block every 40 seconds         600/40=15       15x3=45
dogecoin     SPREAD=30     block every 60 seconds         600/60=10       10x3=30
potcoin      SPREAD=45     block every 40 seconds         600/40=15       15x3=45
craftcoin    SPREAD=6      block every 300 seconds        600/300=2        2x3=6  (old spec)
craftcoin    SPREAD=30     block every 60 seconds         600/60=10       10x3=30 (new spec)
nyancoin     SPREAD=30     block every 60 seconds         600/60=10       10x3=30

It is not a hard limit # of blocks, it is the # times the average work required to solve a block.  In other words, for a SPREAD=3 if the average time to block is 8 hours, then your shares will fall off the payout after 24 hours.  So, if p2pool happens to get lucky and solve 10 blocks in that 24 hour period, your share will be paid for all 10 blocks.



--------------------
To generate unique values for IDENTIFIER and PREFIX create a random string of 19 numbers and convert to Hex.

I use the windows Programmer Calculator to do the conversion (View menu).

Example:
5486237465184378845 = 4C2307E841C11FDD

....more to come!
822  Alternate cryptocurrencies / Mining (Altcoins) / Re: P2Pool Detailed Settings for Altcoins on: February 10, 2014, 02:26:33 AM
p2pool/bitcoin/networks.py

This is where the coin specific settings are stored. All the information in this file needs to come from the source code of each coin and be updated if any of that information is changed.

For reference here is the section of the code for litecoin:
Code:
    litecoin=math.Object(
        P2P_PREFIX='fbc0b6db'.decode('hex'),
        P2P_PORT=9333,
        ADDRESS_VERSION=48,
        RPC_PORT=9332,
        RPC_CHECK=defer.inlineCallbacks(lambda bitcoind: defer.returnValue(
            'litecoinaddress' in (yield bitcoind.rpc_help()) and
            not (yield bitcoind.rpc_getinfo())['testnet']
        )),
        SUBSIDY_FUNC=lambda height: 50*100000000 >> (height + 1)//840000,
        POW_FUNC=lambda data: pack.IntType(256).unpack(__import__('ltc_scrypt').getPoWHash(data)),
        BLOCK_PERIOD=150, # s
        SYMBOL='LTC',
        CONF_FILE_FUNC=lambda: os.path.join(os.path.join(os.environ['APPDATA'], 'Litecoin') if platform.system() == 'Windows' else os.path.expanduser('~/Library/Application Support/Litecoin/') if platform.system() == 'Darwin' else os.path.expanduser('~/.litecoin'), 'litecoin.conf'),
        BLOCK_EXPLORER_URL_PREFIX='http://explorer.litecoin.net/block/',
        ADDRESS_EXPLORER_URL_PREFIX='http://explorer.litecoin.net/address/',
        TX_EXPLORER_URL_PREFIX='http://explorer.litecoin.net/tx/',
        SANE_TARGET_RANGE=(2**256//1000000000 - 1, 2**256//1000 - 1),
        DUMB_SCRYPT_DIFF=2**16,
        DUST_THRESHOLD=0.03e8,
    ),

litecoin=math.Object(
Change litecoin to match the name of the altcoin.

P2P_PREFIX='fbc0b6db'.decode('hex'),
Replace 'fbc0b6db' with the values from main.cpp at pchMessageStart[4] =
Remove all '0x' and combine the rest.

P2P_PORT=9333,
Replace 9333 by looking in protocol.h and finding the 2nd value after GetDefaultPort
Some coins may have this in chainparams.cpp at nDefaultPort =

ADDRESS_VERSION=48,
Look in base58.h and find the value of PUBKEY_ADDRESS

RPC_PORT=9332,
Look in bitcoinrpc.cpp for GetArg("-rpcport", xxxx), xxxx is the RPC_PORT.
Some coins may have this in chainparams.cpp at  nRPCPort =

RPC_CHECK= ... 'litecoinaddress'
Look in bitcoinrpc.cpp after setaccount <
If the altcoin has a 'space' between altcoin and address make sure you include the 'space'.
You can also find this in rpcdump.cpp after dumpprivkey <

SUBSIDY_FUNC=lambda height: 50*100000000 >> (height + 1)//840000,
SUBSIDY_FUNC=lambda height: 'block reward' * 'satoshies' >> (height + 1)//'height where block halves'.
For 'block reward' look in main.cpp for nSubsidy
For 'height where block halves' look in main.cpp for nSubsidy -> nSubsidy >>= (nHeight /
If a coin does not have a height where the block halves take out >> (height + 1)//'height where block halves'

Comment
Pay particular attention to verifying that you have this correct. Not doing so will result in some blocks being rewarded less than their full value.

SUBSIDY_FUNC is only used in some instances.
Quote
Sometimes  removed_fees  contains  None  when P2Pool doesn't know the fee associated with a transaction, such as with old versions of *coind as a result of this old bug. Then, P2Pool has to make a conservative estimate of the subsidy using its computed base subsidy and the sum of the fees it does know.

I have not seen a solution for coins with a random block reward. For random block reward coins some have suggested that the 'block reward' should be set to a low number as a high number would cause the block to be rejected [try to verify].

To do
Determine the correct SUBSIDY_FUNC for coins that decrease by a percentage (WDC, Digibyte).
Determine the correct SUBSIDY_FUNC for coins that have a random block reward (DOGE, LEAF, FLAP PENG, MEOW, etc).



....more to come. For now here are my dirty notes:

BLOCK_PERIOD=
------------------------------------------
target time between blocks
<SECONDS> pulled from src/main.cpp (search for "static const int64 nTargetSpacing")
------------------------------------------

SANE_TARGET_RANGE = (2**256//1000000000 - 1, 2**256//1000 - 1)
No changes for scrypt.
DUMB_SCRYPT_DIFF = 2**16
No changes for scrypt.

DUST_THRESHOLD =
Note about DUST_TRESHOLD: In an effort to reduce the number of very small dust payments hanging around in peoples wallets, it does this by looking at your expected block payment and adjusted the required share difficulty until this is above its DUST_THRESHOLD value.
0.03e8    = 3000000   = 0.03       in satoshis [someone please verify]
1e8       = 100000000 = 0.00000001 in satoshis [someone please verify]
0.001e8   = 100000    = 0.001      in satoshis [someone please verify]
823  Alternate cryptocurrencies / Mining (Altcoins) / P2Pool Detailed Settings for Altcoins on: February 10, 2014, 02:26:20 AM
Since it is so hard to find all the information in one location I thought I would start a thread detailing the changes necessary to make most POW altcoins work with p2pool. Thanks go out to all those who have posted this information elsewhere on the forum.

There are two files that will need to be changed:

p2pool/bitcoin/networks.py
p2pool/networks.py


Will break these down in the next two posts. Over time I will update to reflect new information.

Note: When a coin changes it's spec p2pool needs to be changed to match.
Note: All nodes must run the same code. If there are any changes [some exceptions] it is recommended to start a new p2pool share chain by changing IDENTIFIER and PREFIX and deleting the p2pool/data folder.

I maintain a GitHub that I keep updated of the coins I run on xpool.net here:
https://github.com/CartmanSPC/p2pool

Here are some other popular repositories:
https://github.com/narken/p2pool-altcoins
https://github.com/Rav3nPL/p2pool-rav

Please use caution when using some of these repositories as they may not have been updated to reflect changed coin specs.

Link to the original source by forrestv (BTC, LTC, TRC):
https://github.com/forrestv/p2pool
824  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][CRC] Craftcoin - Portable Minecraft Game Currency w. Economy Plugin on: February 10, 2014, 01:36:01 AM
I have had the daemon running for a few hours and no connections. I even went and added the nodes in the OP.

I need some nodes if I am to get the explorer running again.

Thanks for working on updating the block explorer dreamwatcher. The dev has really dropped the ball here. Will send you a node to add in a PM.
825  Alternate cryptocurrencies / Mining (Altcoins) / Re: Finding p2pool networks.py values for new altcoins on: February 07, 2014, 11:21:47 PM
For SPREAD I use the following formula:

SPREAD=
600/[block time]=x
x*3=spread


Not saying that it is right but it's what I use.

Code:
bitcoin SPREAD=3 block every 600 seconds         Baseline
litecoin SPREAD=12 block every 150 seconds       600/150=4       4x3=12
bbqcoin SPREAD=30 block every 60 seconds         600/60=10       10x3=30
casinocoin SPREAD=60 block every 30 seconds      600/30=20       20x3=60
digitalcoin SPREAD=90 block every 20 seconds     600/20=30       30x3=90  (old spec)
digitalcoin SPREAD=45 block every 40 seconds     600/40=15       15x3=45  (new spec)
worldcoin SPREAD=120 block every 15 seconds      600/15=40       40x3=120 (old spec)
worldcoin SPREAD=60 block every 30 seconds       600/30=20       20x3=60  (new spec)
globalcoin SPREAD=45 block every 40 seconds      600/40=15       15x3=45
dogecoin SPREAD=30 block every 60 seconds        600/60=10       10x3=30
potcoin SPREAD=45 block every 40 seconds         600/40=15       15x3=45
craftcoin SPREAD=6 block every 300 seconds       600/300=2        2x3=6  (old spec)
craftcoin SPREAD=30 block every 60 seconds       600/60=10       10x3=30 (new spec)
826  Alternate cryptocurrencies / Mining (Altcoins) / Re: Finding p2pool networks.py values for new altcoins on: February 07, 2014, 10:47:57 PM
SUBSIDY_FUNC = <X>*<TOTAL COINS>
<X> pulled from ./src/main.cpp (search for "nSubsidy")
<TOTAL COINS> total number of minable coins.

I believe this is incorrect. I think the correct way is:

for litecoin:
SUBSIDY_FUNC=lambda height: 50*100000000 >> (height + 1)//840000,
SUBSIDY_FUNC=lambda height: 'block reward' * 'satoshies' >> (height + 1)//'height where block halves'.

If there is no "halfing" you take out the >> (height + 1)//'height where block halves'

//840000 is the number from main.cpp in nSubsidy -> nSubsidy >>= (nHeight /
827  Alternate cryptocurrencies / Mining (Altcoins) / Re: Finding p2pool networks.py values for new altcoins on: February 07, 2014, 10:37:42 PM
As an example...I believe Ravs git has old specs on some of the coins.
828  Alternate cryptocurrencies / Mining (Altcoins) / Re: Finding p2pool networks.py values for new altcoins on: February 07, 2014, 10:03:34 PM
One of the problems is that coins occasionally change specs (DGC, WDC, CRCx2 and soon CSC...of the ones I track) and p2pool has to be updated to those new coin specs. It is a very hard job to keep up with everything Smiley

I try to stay on top of the coins I use in my git.
829  Alternate cryptocurrencies / Mining (Altcoins) / Re: Finding p2pool networks.py values for new altcoins on: February 07, 2014, 07:33:09 PM
Good stuff tvb.

I have considered starting a new thread outlining the values with the OP being updated as needed but will start by making a few comments on yours.

Quote
P2P_PORT = <COIN PORT>
pulled from ./src/init.cpp
Pulling from that location IMO is not a good idea. Better to pull from the actual code "use" than the notes field in init.cpp.
You can find the P2P_PORT in the coin's source code in the protocol.h file, it's the 2nd value after GetDefaultPort.

Quote
RPC_PORT = <RPCPORT>
<PORT> pulled from src/init.cpp (search for "-rpcport")
Again, pulling from that location IMO is not a good idea. Better to pull from the actual code "use" than the notes field in init.cpp.
You can find RPC_PORT in bitcoinrpc.cpp file, look for GetArg("-rpcport", xxxx), where xxxx is the port.

Quote
DUST_THRESHOLD = 0.03e8
I understand why they want to do this for Litecoin and Bitcoin but for most alts I feel this setting is too high (or low depending on how you look at it). I think most smaller miners (which is what were really addressing here) would appreciate more consistent payments in smaller increments rather than fewer larger payments. I use DUST_THRESHOLD=1e8

Fewer (but larger) payments (I feel) puts off miners. Yes, it does increase the number of transactions in their wallet and may cost them more in fees when they try to use them but implementing coin control from newer litecoin releases can help there. They can also split up their transactions or wait for sufficient coin age.

Ok, those are my inputs. Smiley
830  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][CRC] Craftcoin - Portable Minecraft Game Currency w. Economy Plugin on: February 07, 2014, 12:17:20 AM
Just as an FYI currently the old blockchain is on 32222 with a diff of 11.663 and the new blockchain is on 32968 with a diff of 1.25811096.
831  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][CRC] Craftcoin - Portable Minecraft Game Currency w. Economy Plugin on: February 07, 2014, 12:04:26 AM
Has anyone informed Cryptsy? I would think they would need to take action to protect their users...

Whats interesting is that the GitHub codebase for Craftcoin originally had block 35000 set to be the changeover time and then was reduced to 32000 13 days ago  Embarrassed

https://github.com/craftcoin/craftcoin/commit/0e08e7b7d1093157de6915b04ca1a32289d9f90f

It specifies a "Mandatory update to v1.2.0.0" but there are no announcements made anywhere about this outside of GitHub?! I only happened to notice that people started posting about the new 1.2 version in this thread and voiced my concern then.

xpool.net is on the new coin spec.
832  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][CRC] Craftcoin - Portable Minecraft Game Currency w. Economy Plugin on: February 06, 2014, 06:05:36 AM
Well, I tried to warn about this earlier in the thread but it looks like craftcoin forked it's blockchain   Undecided

Most are still on the old 10 coins per block blockchain.

This block explorer is on the old version:

http://crc.cryptocoinexplorer.com/chains

You can see blocks still being found there...there are going to be some unhappy people I imagine.

I'm sure cryptsy is on the old version too...    Cry
833  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][POT] PotCoin Launches Today 01/21 @ 4:20 on: February 06, 2014, 01:46:30 AM
Opened a new Potcoin p2pool node at xpool.net

Mining Port:
stratum+tcp://xpool.net:9420

Stats:
http://xpool.net:9420

Example Connection String:
cgminer -o stratum+tcp://xpool.net:9420 -u YourWalletAddress -p password --scrypt --queue 0 --scan-time 5 --expiry 20
834  Bitcoin / Pools / Re: Why is p2pool as small as it is? on: February 05, 2014, 11:08:43 PM
P2Pool also works differently than any other pool. Such as:

The p2pool sharechain (that stores the PPLNS payment data) has a target speed of 30 seconds per block, which causes a lot of restart message spam to the miner.

Finding a share for a smaller miner can take a while, some miners believe this means they are getting "ripped off" because they don't understand variance.

Orphans/DOAs on the sharechain are common because of the fast target speed, some miners misunderstand this to be similar to orphaned blocks on the blockchain. As long as the orphan rate of shares between p2pool nodes is similar, then it isn't impacting miner payouts at all. (This is reflected in p2pool's Efficiency stat in the default interfaces.)

P2Pool is quite cool, as an experiment and to learn more about it I'm running some nodes on a new alt coin. I think the issues above can mostly be resolved with better miner education. Some way to reduce variance for smaller miners would be nice though.

Thank you for your post roy7!

Added the following to the FAQ section on my nodes:
--------------
Q: How is P2Pool different?
A:The P2Pool sharechain is different than the coin blockchain. It has a target speed of 30 seconds per block (Bitcoin) which causes a lot of restart messages to the miner.

Smaller miners may take some time to find a share. This will result in an increase of variance but over time you should experience higher payouts when compared to other pools.

Orphans/DOAs on the P2Pool sharechain are common because of the fast target speed. Do not confuse this with orphaned blocks on the coin blockchain. Refrence the efficiency stat of your P2Pool node.
--------------
Hope you don't mind that I reworded it some Smiley
835  Alternate cryptocurrencies / Announcements (Altcoins) / Re: Official Anoncoin chat thread (including history) on: February 05, 2014, 10:38:04 PM
this happens when i2p is not running, or if the client SAM inside i2p isnt enabled.
if you disable i2p, it stops trying to connect to it.

Thanks K1773R. Still happens with stfu=1  :/
Its ok though as a new terminal window stops it from displaying.
836  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][CRC] Craftcoin - Portable Minecraft Game Currency w. Economy Plugin on: February 05, 2014, 06:59:50 PM
New Craftcoin coin specs uploaded to GitHub: https://github.com/CartmanSPC/p2pool
 
Use AFTER block 32000 and with wallet >= 1.2.0.0!
Please delete your craftcoin data folder (p2pool/data/craftcoin) before using these new specs.
 
Details:
5 minute blocks to 1 minute blocks
10 coins per block to 2 coins per block
Changed SHARE_PERIOD to allow for more shares.
Reduced CHAIN_LENGTH to equal REAL_CHAIN_LENGTH.
SPREAD changed according to the new block time.
IDENTIFIER/PREFIX changed to only connect pools with the new spec.
837  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [GLC] Global Coin Group MANDATORY UPDATE! | Released | Store Being Updated! on: February 05, 2014, 05:22:06 AM
Opened a new Globalcoin p2pool node at xpool.net


Mining Port:
stratum+tcp://xpool.net:8860

Stats:
http://xpool.net:8860

Example Connection String:
cgminer -o stratum+tcp://xpool.net:8860 -u YourWalletAddress -p password --scrypt --queue 0 --scan-time 5 --expiry 20
838  Alternate cryptocurrencies / Announcements (Altcoins) / Re: Official Anoncoin chat thread (including history) on: February 05, 2014, 02:11:10 AM
I keep getting the following error when running anoncoind on Ubantu:

Failed to connect to SAM(111)
Created a new SAM session (HNTTJ)  from another (BEILZLXM)
Closing SAM session (HNTTJ) ...
Failed to connect to SAM(111)
Failed to connect to SAM(111)
Created a new SAM session (DVMENQNO)  from another (BEILZLXM)
Closing SAM session (DVMENQNO) ...
Failed to connect to SAM(111)
Failed to connect to SAM(111)
Created a new SAM session (EACKRGSQ)  from another (BEILZLXM)
Closing SAM session (EACKRGSQ) ...
Failed to connect to SAM(111)
Failed to connect to SAM(111)
Created a new SAM session (LKDHF)  from another (BEILZLXM)
Closing SAM session (LKDHF) ...
Failed to connect to SAM(111)


Is this normal? It's quite annoying to see it.

Also, the build from: https://github.com/Anoncoin/anoncoin
state:     "errors" : "This is a pre-release test build - use at your own risk - do not use for mining or merchant applications"

Should I be using a different version?

Thanks!

Edit: I only allow specific ports open (going out) so if there is a port that need to be opened other than the usual ones for anoncoind please let me know.
839  Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][CSC] CasinoCoin - The Premiere Coin for Online Casino Gaming | On Cryptsy! on: February 05, 2014, 01:58:44 AM
I have added Casinocoin to my Game site http://CryptoWheel.net

P.S. This particular game was sponsored by Cart from http://xpool.net  -  Now offering a Casinocoin pool

Give this casino a try. It's legit. I told them we were looking for places to gamble so I let them borrow my personal Casinocoin to get started Smiley
840  Alternate cryptocurrencies / Altcoin Discussion / Re: P2Pool source code support thread for DGC - WDC - CRC - CSC - ANC on: February 01, 2014, 12:40:46 AM
Moving this thread to:

https://cryptocointalk.com/topic/4062-p2pool-source-code-support/
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 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 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!