Search content
Sort by
Showing 20 of 38 results by tvb
Re: ★★ DigiByte ★★ [DGB] DigiShield v2.0 Now Live ✈ Mandatory Update ✔
2) Transactional Currency:With 21 billion coins, DigiByte will primarily become a worldwide currency traded for goods & services, and not a volatile speculative commodity like Bitcoin. DigiByte has a natural ratio of 1BTC:1000DGB to Bitcoin. This means that if Bitcoin is worth $1,000 DigiByte should be worth $1 -$10. A Perfect price for buying goods & services. No one likes to look in their wallet and see that they have 0.001 coins; 1,000 DigiBytes are much more appealing.
DigiRoadMap 2014
Community Reward Bounties
Promotional Video 1 Million DigiByte Reward Digiman Marketing Images Take the existing DigiMan and put him in several other poses. 500,000 DGB
How To Guides Short concise professional guides explaining how to do various tasks related to DigiByte. 25,000 DGB per guide.
This is ridiculous, if you first state that DigiByte should be worth between 1$ and $10 and then reward DGB 1,000,000 for a Promotional Video you are effectively rewarding a minimal $1,000,000 for one to create a sub 30seconds video.. the reward should be DGB 1000 at most!
@DigiByte, I would like to receive a official response and your point-of-view on this subject.
Re: ★★ DigiByte ★★ [DGB] DigiShield v2.0 Now Live ✈ Mandatory Update ✔
2) Transactional Currency:With 21 billion coins, DigiByte will primarily become a worldwide currency traded for goods & services, and not a volatile speculative commodity like Bitcoin. DigiByte has a natural ratio of 1BTC:1000DGB to Bitcoin. This means that if Bitcoin is worth $1,000 DigiByte should be worth $1 -$10. A Perfect price for buying goods & services. No one likes to look in their wallet and see that they have 0.001 coins; 1,000 DigiBytes are much more appealing.
DigiRoadMap 2014
Community Reward Bounties
Promotional Video 1 Million DigiByte Reward Digiman Marketing Images Take the existing DigiMan and put him in several other poses. 500,000 DGB
How To Guides Short concise professional guides explaining how to do various tasks related to DigiByte. 25,000 DGB per guide.
This is ridiculous, if you first state that DigiByte should be worth between 1$ and $10 and then reward DGB 1,000,000 for a Promotional Video you are effectively rewarding a minimal $1,000,000 for one to create a sub 30seconds video.. the reward should be DGB 1000 at most!
Re: ★★ DigiByte ★★ [DGB] A Professional Cryptocurrency ✈ Android Wallet, CoinedUp ✔
Uh... It's not a good sign when half of page posts displays "This user is ignored". That's why you should use self-moderated thread...
Ohhh, thank you for pointing out this feature. Much appreciated
Re: ★★ DigiByte ★★ [DGB] A Professional Cryptocurrency ✈ Android Wallet, CoinedUp ✔
Can we please stop flooding this thread with pool advertisements? I find it really annoying and makes me stop coming back to this thread, which will lead in losing interest in DGB eventually. Which in itself is bad because I have an open order of 1.7BTC at coinmarket.io which needs to be filled 
Re: ★★ DigiByte ★★ [DGB] A Professional Cryptocurrency ✈ Android Wallet, CoinedUp ✔
Meh, better to style it orange. See https://www.google.nl/search?q=netherlands+orange&espv=210&es_sm=119&source=lnms&tbm=isch&sa=X&ei=qtj7Up_wLYX80QWA-IGAAg&ved=0CAkQ_AUoAQ&biw=1440&bih=802
Re: ★★ DigiByte ★★ [DGB] A Professional Cryptocurrency ✈ Android Wallet, CoinedUp ✔
@CoinMarketio 49m
Downtime for the bitcoin wallet maintenance is starting shortly. Expected duration is 45 minutes or less.
Re: ★★ DigiByte ★★ [DGB] A Professional Cryptocurrency ✈ Android Wallet, CoinedUp ✔
you forget the neatherlands!
Netherlands, that is.
PERSIST=True
You need to set it to False to bootstrap the sharechain, but once you've done that and have a bootstrap node up, set it to True
It prevents anyone else from bootstrapping a sharechain
You need to set it to False to bootstrap the sharechain, but once you've done that and have a bootstrap node up, set it to True
It prevents anyone else from bootstrapping a sharechain
SUBSIDY_FUNC = *
pulled from ./src/main.cpp (search for "nSubsidy")
total number of minable coins.
pulled from ./src/main.cpp (search for "nSubsidy")
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 /
Thank you! I have updated my post to reflect your corrections.
Developers of new alt-coins should also release the right p2pool config immediately when a coin is launched.
This should become a standard practice, so that every p2pool node uses the exact same configuration creating one homogeneous mega pool. I've seen multiple p2pools for the same coin because multiple persons create different configurations. P2pool is pretty useless if the nodes for the same coin do not all act as one.
I like p2pool a lot but I still fail to find correct configurations for new alt-coins.
This should become a standard practice, so that every p2pool node uses the exact same configuration creating one homogeneous mega pool. I've seen multiple p2pools for the same coin because multiple persons create different configurations. P2pool is pretty useless if the nodes for the same coin do not all act as one.
I like p2pool a lot but I still fail to find correct configurations for new alt-coins.
Yes I agree completely! How can we enforce this?
I think
https://github.com/Rav3nPL/p2pool-rav.git
has the most complete network.py files for most altcoins. So if you want to add a new coin, probably the best way would be to clone that and do a merge request afterwards. That way there won't be 1001 different versions of p2pool on github, each of them working for exactly one altcoin
Just my 2 cent.
... and thanks a lot @TVB for the hard facts.
Yeah, only if people would submit a merge request. That would be ideal.
I will probably start a new fork especially for that.
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.
...
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.
...
I agree, although forrestv really should add it to the p2pool wiki or p2pool.info website
And you are right. 'pulling' the actual configured values from the source is better. Thanks for that!
I think we can now focus on the p2pool specific networks.py values..
Fantastic post TVB. Only item you didn't list was SPREAD which I believe is the # of blocks worth of work to pay out, ie the PPLNS window size (N being SPREAD # of blocks of work).
I will soon follow up with details about the /networks.py file which is not coin specific but p2pool specific and thus different from /bitcoin/networks.py!
/networks.py contains the SPREAD value etc.
So, I had a little chat with forrestv! Here is some information on how to find the correct settings for the /bitcoin/networks.py file.
Attention: the /bitcoin/networks.py is COIN SPECIFIC
Sample /bitcoin/networks.py:
=math.Object(
P2P_PREFIX=''.decode('hex'),
P2P_PORT=,
ADDRESS_VERSION=,
RPC_PORT=,
RPC_CHECK=defer.inlineCallbacks(lambda bitcoind: defer.returnValue(
'address' in (yield bitcoind.rpc_help()) and
not (yield bitcoind.rpc_getinfo())['testnet']
)),
SUBSIDY_FUNC=lambda height: * >> (height + 1)//840000,
POW_FUNC=lambda data: pack.IntType(256).unpack(__import__('ltc_scrypt').getPoWHash(data)),
BLOCK_PERIOD=, # s
SYMBOL='',
CONF_FILE_FUNC=lambda: os.path.join(os.path.join(os.environ['APPDATA'], '') if platform.system() == 'Windows' else os.path.expanduser('~/Library/Application Support//') if platform.system() == 'Darwin' else os.path.expanduser('~/.'), '.conf'),
BLOCK_EXPLORER_URL_PREFIX='',
ADDRESS_EXPLORER_URL_PREFIX='',
TX_EXPLORER_URL_PREFIX='',
SANE_TARGET_RANGE=(2**256//1000000000 - 1, 2**256//1000 - 1),
DUMB_SCRYPT_DIFF=2**16,
DUST_THRESHOLD=0.03e8,
),
Detailed explanation
P2P_PREFIX =
pulled from ./src/main.ccp (search for "unsigned char pchMessageStart" and use the value between { } (remove all 0x))
P2P_PORT =
pulled from ./src/protocol.h (search for "GetDefaultPort", 2nd value will be the port value.)
ADDRESS_VERSION =
pulled from ./src/base58.h (search for "PUBKEY_ADDRESS")
RPC_PORT =
pulled from ./src/bitcoinrpc.cpp (search for 'GetArg("-rpcport", xxxx)' where xxxx is the value of the port.
RPC_CHECK change e.g. 'litecoinaddress' to 'address'
SUBSIDY_FUNC = * >> (height + 1)//
pulled from ./src/main.cpp (search for "nSubsidy")
pulled from ./src/main.cpp (search for "nSubsidy >>= (nHeight")
note: If there is no "halfing" you should take out the ">> (height + 1)//"
BLOCK_PERIOD =
pulled from ./src/main.cpp (search for "static const int64 nTargetSpacing")
SYMBOL =
Like BTC, LTC, DOGE
CONF_FILE_FUNC = change , , and
BLOCK_EXPLORER_URL_PREFIX =
ADDRESS_EXPLORER_URL_PREFIX =
TX_EXPLORER_URL_PREFIX =
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 = 0.03e8
No changes for scrypt.
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 (current 0.1000).
Transaction fees in Litecoin have been designed to protect the network from a problem known as transaction spam (dust transactions). If someone was to setup a loop between two wallets, sending back and forth small amounts, they would grow the block chain. Fees prevent this as it becomes too expensive to do this.[/size]
Attention: the /bitcoin/networks.py is COIN SPECIFIC
Sample /bitcoin/networks.py:
Code:
=math.Object(
P2P_PREFIX=''.decode('hex'),
P2P_PORT=,
ADDRESS_VERSION=,
RPC_PORT=,
RPC_CHECK=defer.inlineCallbacks(lambda bitcoind: defer.returnValue(
'address' in (yield bitcoind.rpc_help()) and
not (yield bitcoind.rpc_getinfo())['testnet']
)),
SUBSIDY_FUNC=lambda height: * >> (height + 1)//840000,
POW_FUNC=lambda data: pack.IntType(256).unpack(__import__('ltc_scrypt').getPoWHash(data)),
BLOCK_PERIOD=, # s
SYMBOL='',
CONF_FILE_FUNC=lambda: os.path.join(os.path.join(os.environ['APPDATA'], '') if platform.system() == 'Windows' else os.path.expanduser('~/Library/Application Support//') if platform.system() == 'Darwin' else os.path.expanduser('~/.'), '.conf'),
BLOCK_EXPLORER_URL_PREFIX='',
ADDRESS_EXPLORER_URL_PREFIX='',
TX_EXPLORER_URL_PREFIX='',
SANE_TARGET_RANGE=(2**256//1000000000 - 1, 2**256//1000 - 1),
DUMB_SCRYPT_DIFF=2**16,
DUST_THRESHOLD=0.03e8,
),
Detailed explanation
P2P_PREFIX =
pulled from ./src/main.ccp (search for "unsigned char pchMessageStart" and use the value between { } (remove all 0x))
P2P_PORT =
pulled from ./src/protocol.h (search for "GetDefaultPort", 2nd value will be the port value.)
ADDRESS_VERSION =
pulled from ./src/base58.h (search for "PUBKEY_ADDRESS")
RPC_PORT =
pulled from ./src/bitcoinrpc.cpp (search for 'GetArg("-rpcport", xxxx)' where xxxx is the value of the port.
RPC_CHECK change e.g. 'litecoinaddress' to 'address'
SUBSIDY_FUNC = * >> (height + 1)//
pulled from ./src/main.cpp (search for "nSubsidy")
pulled from ./src/main.cpp (search for "nSubsidy >>= (nHeight")
note: If there is no "halfing" you should take out the ">> (height + 1)//"
BLOCK_PERIOD =
pulled from ./src/main.cpp (search for "static const int64 nTargetSpacing")
SYMBOL =
Like BTC, LTC, DOGE
CONF_FILE_FUNC = change , , and
BLOCK_EXPLORER_URL_PREFIX =
ADDRESS_EXPLORER_URL_PREFIX =
TX_EXPLORER_URL_PREFIX =
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 = 0.03e8
No changes for scrypt.
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 (current 0.1000).
Transaction fees in Litecoin have been designed to protect the network from a problem known as transaction spam (dust transactions). If someone was to setup a loop between two wallets, sending back and forth small amounts, they would grow the block chain. Fees prevent this as it becomes too expensive to do this.[/size]