Pebblecoin (XPB) - FIRST DPOS CRYPTONOTE COIN LIVE - Qt Wallet GUI - v0.4.4.1

[XPB]

Pebblecoin

UPDATE 2015/12/31: Version 0.4.4.1 is now out.  The major change is optimizing the daemon to use less RAM.  It no longer keeps all the blocks, which are rarely needed, in RAM, and so RAM usage has decreased from around 2 gigabytes, to under 200 megabytes.  Mac binaries are also now available.  The new wallet is compatible with the old wallet - simply turn off the old wallet, and start the new wallet, and the blockchain will update automatically to use less RAM.

Code:

Release Notes 0.4.4.1
- (All) Fix blockchain RAM usage, from almost 2 GB to less than 200 MB
  - Seamless blockchain conversion on first run with new binaries
- (Qt) Fix high CPU usage
- (Qt) Fix sync indicator (# of total blocks)
- (Mac) Mac binaries
- Technical Notes:
  - (All) Blockchain disk-backed storage with sqlite3 and stxxl
  - (Mac) Fix mac compilation
  - (All) Update build files & instructions for linux, mac, windows
  - (All) Remove unused protobuf and OpenSSL dependencies for Qt wallet
  - (Tests) Fix valgrind errors
  - (Tests) Use local directory for blockchain instead of default directory
  - (Tests) Run tests on Windows if using new enough MSVC

LINKS:
Windows 64-bit: https://www.dropbox.com/s/b4kubwwnb4t7o4w/pebblecoin-all-win32-x64-v0.4.4.1.zip?dl=0
Mac 64-bit: https://www.dropbox.com/s/uoy9z1oxu4x53cv/pebblecoin-all-mac-x64-v0.4.4.1.tar.gz?dl=0
Linux 64-bit: https://www.dropbox.com/s/jq3h3bc29jmndks/pebblecoin-all-linux-x64-v0.4.4.1.tar.gz?dl=0

Exchange: https://poloniex.com/exchange#btc_xpb .

Source: https://github.com/xpbcreator/pebblecoin/

CONTACT: xpbcreator@torguard.tg
IRC: irc.freenode.net, #pebblecoin


UPDATE 2015/06/08: Version 0.4.3.1 is now out.  This is a minor, mostly bug-fix release.  Work continues on the next major release which will bring us user-created currencies and user-graded contracts. Release notes:

Code:

Release Notes 0.4.3.1
- RPC calls for DPOS:
  - getdelegateinfos RPC call
  - get kimageseqs RPC call
  - block header contains signing_delegate_id
- fix checkpoint rollback bug
- fix inability to send coins if voting history was lost

UPDATE 2015/05/04: Version 0.4.2.2 is now out.  This is a bug-fix/cosmetic release.  Release notes:

• Payment ID support
• Windows installer
• Logos updated
• Improved DPOS tab
• Sync issues fully fixed
• Fix rare crash bug
• Fix min out 0 bug
• Fix debit display
• Fix GUI not updating
• Updated hard-coded seed nodes

UPDATE 2015/04/24: The switch-over to DPOS has succeeded without a hitch!  DPOS blocks are being signed as we speak, at the far faster pace of 15 seconds per block.  This marks the start of a new era for Pebblecoin.


UPDATE 2015/04/21: Congratulations to the first registered delegate!  This indicates the start of the forking change so everybody please update your daemons if you haven't already.  

To promote the coin and encourage people to become delegates, we've come up with an incentive scheme.

First, we'll send a free 100 XPB to anybody who PMs me their public address, for people to play around with and to start using the coin.

Second, once DPOS starts, for the first month of DPOS I'll send an extra 0.5 XPB to the signing delegate for every block they process.  This is on top of the usual transaction fees they will receive.  This is to encourage more people to become delegates at this important phase of the coin.


UPDATE 2015/04/19: All went well on the testnet release, so after a few further minor modifications, we are releasing version 0.4.1.2 to the public.  This is a forking change, so please update your clients and servers (links below).  At block 83120, sometime on April 21st, registration for DPOS delegates will begin.  At block 85300, sometime on April 24th, the network will switch over to DPOS.  As with the testnet, to become a delegate and receive block fees for securing the network, just turn on your wallet, register to be a delegate (5 XPB fee), and then leave your wallet on.  It will sign the blocks when it is your turn.

While Roman works on the next phase of the release - introducing subcurrencies - I will be fixing up some loose ends on the wallet, adding payment ID support, etc.

This is truly an exciting time for Pebblecoin.

RELEASE NOTES:

• All clients adjust internal clocks using ntp (client list in src/common/ntp_time.cpp)
• Added testnet support
• DPOS registration starts Block 83120 (~April 21st)
• DPOS phase starts Block 85300 (~April 24th)
• Default fee bumped to 0.10 XPB
• Low-free transactions no longer get relayed by default
• Significantly improved wallet sync
• Checkpoint at Block 79000

TOTAL CURRENT COINS: Available at this link.
BLOCK TARGET TIME: 2 minutes
EXPECTED EMISSION:
At Block 3600 (End of Day 5): ~78 XPBs
At Block 6480 (End of Day 9): ~758 XPBs
At Block 9360 (End of Day 13): 6,771.0 XPBs
At Block 12240 (End of Day 17): ~61,000 XPBs
At Block 15120 (End of Day 21): ~550,000 XPBs, start of regular 300/block emission
At Block 21900 (End of Month 1): ~2,600,000 XPBs, 300/block
At Block 43800 (End of Month 2): ~9,150,000 XPBs, 300/block
At Block 85300 (End of POW phase): ~21,500,300 XPBs.


UPDATE: The Pebblecoin Pool is now live!

Instructions: Download the linux miner and run it: ./minerd -o stratum+tcp://69.60.113.21:3350 -u YOUR_WALLET_ADDRESS -p x


UPDATE: The Pebblecoin wallet is now live!




There have been thousands of attempts at alternative currencies in the community.  Many are 100% copies of existing blockchains with a different name.  Some are very slight variations with no significant differences.  From recent history it is apparent the only realistic chance for viability of a new currency is one that is innovation and continued support and development.  The bitcoin community for good reason has shown interest in currencies that provide privacy of transactions, several currencies such as darkcoin, have become popular based on this desire.  The best technology for privacy is cryptonote although for a variety of reasons there hasnt been much development for ease of use, and as a result there has not been significant adoption.

Pebblecoin (XPB) is a cryptonote based coin with improvements and changes in some areas, and the promise of development in others.  I invite developers to work on this technology with me.  There is no premine, any tips or support of any developer including myself will be completely voluntary.  These are the following areas which I have determined needs changes/updates:
I welcome suggestions, and am interested what else I can try to improve.

1) New Mining algorithm (active)

A mining algorithm is either susceptible to ASIC development or to being botnetted, meaning it is either more efficient to have a centralized mining entity (as is the case with bitcoin) or to have an algorithm that requires a real CPU, in which case botnets become very attractive.  To my knowledge there does not exist a blockchain that attempts to solve both problems, by having an algorithm that only works on a general purpose computer and is difficult to botnet.  Cryptonote coins currently are primarily mined with botnets.

Boulderhash is a new mining algorithm requiring 13 GB RAM, nearly eliminating all possible zombie (botnet controlled) computers from mining.  Most infected computers in the world do not have 13 GB available, so an algorithm that requires that much RAM severely limits the productivity of a botnet.  13 GB also makes ASICs cost prohibitive, and the current GPUs do not have that much RAM.  What's left is general purpose computers as was the original intent of bitcoin's mining process.

2) Distribution of coins (active)

It is very common in the launch of a new cryptocurrency the distribution algorithm heavily is weighted towards the very early adopters.  Such distribution is designed to give a massive advantage to people who are fully prepared to mine at launch, with a very large difference shortly after sometimes a few days later.  If the point of mining is to both secure the network and fairly distribute coins a gradual build up of rewards makes more sense, with no drop off in mining rewards.  At a standard block reward of 300, at launch each block will reward 0.3 coins leading up to 3, 30, and finally the standard reward of 300 which will be the standard unchanging reward from that point.  It will take approximately 3 weeks for the block reward of 300 to be reached.

3) GUI Software (active)

There are no current cryptonote coins that have a downloadable GUI, which makes the user experience much worse than that of bitcoin.  It is hard to achieve signficant adoption with a command line interface.  The very first update had the exact GUI written for bitcoin fully working with Pebblecoin.  The GUI was released on Jan 19, before the full 300 XPB reward was awarded for winning the block.

4) IRC Chat support embedded in Client GUI (active)

For user support, and to talk to core developers message boards such as Bitcointalk and reddit are primarily used.  I have embedded an IRC client in the GUI and be available at set hours for any kind of support.

5) Address aliasing (to be worked on)

Just as a user visiting google does not need to know the ip address, similarly an address should have the ability to have an associated userid.  If I ask a friend to send me pebblecoins it would be easier to tell him send it to @myuserid rather than a very long address or scanning a QR code.  There should be a way of registering a userid on the blockchain that will permanently translate to a pebblecoin addresss.


QT INSTRUCTIONS:

• Download the package for your respective platform
• Run the Qt executable.  The software will generate a new wallet for you and use a default folder: ~/.pebblecoin on Linux and %appdata%\pebblecoin on Windows.
• To use an existing wallet, copy the wallet.keys file into the default folder.
• To use a different data directory and/or wallet file, run the software like so: ./pebblecoin-qt --data-dir <DataDir> --wallet-file <FileName>.
• To enable mining, run the start_mining_NEEDS_13GB_RAM.bat batch file. Or run the qt wallet with the --enable-boulderhash command line option, or put enable-boulderhash=1 into the config file.  It will start mining to the wallet address.  To change the number of mining threads (13GB required per thread), do --mining-threads <NumThreads> or edit the batch file.

DAEMON + SIMPLEWALLET INSTRUCTIONS:

• Download the package, run: ./pebblecoind --data-dir pebblecoin_data
• Once the daemon finished syncing, run the simplewallet: ./simplewallet

POOL INSTRUCTIONS:

• Download the miner binary for your platform.
• Run the miner using a wallet address gotten from simplewallet or the Qt Wallet:
  

Code:

minerd -o stratum+tcp://69.60.113.21:3350 -u YOUR_WALLET_ADDRESS -p x

[/li]

DEV WALLET (for donations):
PByFqCfuDRUPVsNrzrUXnuUdF7LpXsTTZXeq5cdHpJDogbJ8EBXopciN7DmQiGhLEo5ArA7dFqGga2A AhbRaZ2gL8jjp9VmYgk

[1715396600]

1715396600

[1715396600]

1715396600

[1715396600]

1715396600

[1715396600]

1715396600

[dodgecharger]

first in 2015 

[Coin-Moron]

Waiting . .

[Riseman]

Tried to set up mining. And then realized that my non-zombie PC doesn't have enough RAM 

[PeaMine]

2015-Jan-01 04:49:13.046253 Provided incorrect block id hash hex. Given 3b0e3ff57a8ea1ae614c6b648999be35838c0edbd24a2c2e18303ad135ac43b9, but block hashed to 48295246f3c9f48b39d945c205abfdb754c80b32f654d7d34a390de533f2de3a

[Vorksholk]

Daemon startup appears to fail.
OS: Ubuntu 14.04 x64

Command: ./pebblecoind --data-dir ~/pebblecoin_data/ --genesis-nonce-string "30/Dec/2014 NASDAQ 4777.44 DAX 9805.55 DOW 17983.13" --genesis-timestamp 1419973386 --genesis-coinbase-hex 010a01ff0000210179e231c0574796ecc198e05afaecd3aea2d9a84fa6c51088eb75130c4eb4da7 2 --genesis-id-hash-hex 3b0e3ff57a8ea1ae614c6b648999be35838c0edbd24a2c2e18303ad135ac43b9

Console output:

2014-Dec-31 21:59:08.550854 Starting...
2014-Dec-31 21:59:08.551935 pebblecoin v0.1.0.4()
2014-Dec-31 21:59:08.552067 Module folder: ./pebblecoind
2014-Dec-31 21:59:08.552257 Genesis block nonce is: 2619793676
2014-Dec-31 21:59:08.552388 Initializing global hash cache...
2014-Dec-31 21:59:08.552476 Loading hash cache...
2014-Dec-31 21:59:08.552671 Can't load hash cache from file /root/pebblecoin_data//hashcache.bin, no genesis block hashes provided
2014-Dec-31 21:59:08.552767 Hash cache initialized, have 0 hashes and 0 signed hashes
2014-Dec-31 21:59:08.552861 Global hash cache initialized OK...
2014-Dec-31 21:59:08.553215 Initializing shared boulderhash state...
2014-Dec-31 21:59:08.553305 Malloc'ing boulderhash state...
2014-Dec-31 21:59:08.554101 Shared boulderhash state initialized OK
2014-Dec-31 21:59:08.554191 Initializing boulderhash threadpool...
2014-Dec-31 21:59:08.555282 Started 16 boulderhash worker threads
2014-Dec-31 21:59:08.555376 Initializing p2p server...
2014-Dec-31 21:59:08.555531 Binding on 0.0.0.0:6180
2014-Dec-31 21:59:08.555834 Net service binded on 0.0.0.0:6180
2014-Dec-31 21:59:08.555926 Attempting to add IGD port mapping.
2014-Dec-31 21:59:12.561207 No IGD was found.
2014-Dec-31 21:59:12.561812 P2p server initialized OK
2014-Dec-31 21:59:12.562095 Initializing cryptonote protocol...
2014-Dec-31 21:59:12.562379 Cryptonote protocol initialized OK
2014-Dec-31 21:59:12.562662 Initializing core rpc server...
2014-Dec-31 21:59:12.562968 Binding on 127.0.0.1:6181
2014-Dec-31 21:59:12.563392 Core rpc server initialized OK on port: 6181
2014-Dec-31 21:59:12.563661 Initializing core...
2014-Dec-31 21:59:12.563945 Loading blockchain...
2014-Dec-31 21:59:12.564233 Can't load blockchain storage from file, generating genesis block.
2014-Dec-31 21:59:12.564532 Genesis block nonce is: 2619793676
2014-Dec-31 21:59:53.477973 Blockchain initialized. last block: 0, d1.h7.m56.s47 time ago, current difficulty: 1
2014-Dec-31 21:59:53.478172 Core initialized OK
2014-Dec-31 21:59:53.478325 Starting core rpc server...
2014-Dec-31 21:59:53.478368 Run net_service loop( 2 threads)...
2014-Dec-31 21:59:53.478955 [SRV_MAIN]Core rpc server started ok
2014-Dec-31 21:59:53.479083 [SRV_MAIN]Starting p2p net loop...
2014-Dec-31 21:59:53.479193 [SRV_MAIN]Run net_service loop( 10 threads)...
2014-Dec-31 21:59:53.484037 [P2P4][69.60.112.169:59166 INC]Sync data returned unknown top block: 1 -> 353 [352 blocks (0 days) behind]
SYNCHRONIZATION started
2014-Dec-31 21:59:53.484178 [P2P0][69.60.113.24:35685 INC]Sync data returned unknown top block: 1 -> 353 [352 blocks (0 days) behind]
SYNCHRONIZATION started
2014-Dec-31 21:59:53.484672 [P2P3][69.60.112.164:41740 INC]Sync data returned unknown top block: 1 -> 353 [352 blocks (0 days) behind]
SYNCHRONIZATION started
2014-Dec-31 21:59:53.484678 [P2P1][54.87.190.112:36705 INC]Sync data returned unknown top block: 1 -> 353 [352 blocks (0 days) behind]
SYNCHRONIZATION started
2014-Dec-31 21:59:53.484762 [P2P2][69.60.113.23:43735 INC]Sync data returned unknown top block: 1 -> 353 [352 blocks (0 days) behind]
SYNCHRONIZATION started
2014-Dec-31 21:59:53.552038 [P2P5]ERROR ../../src/cryptonote_core/blockchain_storage.cpp:1154 Client sent wrong NOTIFY_REQUEST_CHAIN: genesis block missmatch:
id: <80e28ab82d17e61319309c7525d2f76a78731d0c6099b646bce2948d670181ff>,
expected: <3b0e3ff57a8ea1ae614c6b648999be35838c0edbd24a2c2e18303ad135ac43b9>,
 dropping connection
2014-Dec-31 21:59:53.552277 [P2P5]ERROR ../../src/cryptonote_protocol/cryptonote_protocol_handler.inl:469 [69.60.112.164:41740 INC]Failed to handle NOTIFY_REQUEST_CHAIN.
2014-Dec-31 21:59:53.553020 [P2P8]ERROR ../../src/cryptonote_core/blockchain_storage.cpp:1154 Client sent wrong NOTIFY_REQUEST_CHAIN: genesis block missmatch:
id: <80e28ab82d17e61319309c7525d2f76a78731d0c6099b646bce2948d670181ff>,
expected: <3b0e3ff57a8ea1ae614c6b648999be35838c0edbd24a2c2e18303ad135ac43b9>,
 dropping connection
2014-Dec-31 21:59:53.553156 [P2P8]ERROR ../../src/cryptonote_protocol/cryptonote_protocol_handler.inl:469 [69.60.113.23:43735 INC]Failed to handle NOTIFY_REQUEST_CHAIN.
2014-Dec-31 21:59:53.554366 [P2P8]ERROR ../../src/cryptonote_core/blockchain_storage.cpp:1154 Client sent wrong NOTIFY_REQUEST_CHAIN: genesis block missmatch:
id: <80e28ab82d17e61319309c7525d2f76a78731d0c6099b646bce2948d670181ff>,
expected: <3b0e3ff57a8ea1ae614c6b648999be35838c0edbd24a2c2e18303ad135ac43b9>,
 dropping connection
2014-Dec-31 21:59:53.554497 [P2P8]ERROR ../../src/cryptonote_protocol/cryptonote_protocol_handler.inl:469 [69.60.112.169:59166 INC]Failed to handle NOTIFY_REQUEST_CHAIN.
2014-Dec-31 21:59:54.278150 [P2P4][69.60.113.24:35688 INC]Sync data returned unknown top block: 1 -> 354 [353 blocks (0 days) behind]
SYNCHRONIZATION started
2014-Dec-31 21:59:54.388163 [P2P4]ERROR ../../src/cryptonote_core/blockchain_storage.cpp:1154 Client sent wrong NOTIFY_REQUEST_CHAIN: genesis block missmatch:
id: <80e28ab82d17e61319309c7525d2f76a78731d0c6099b646bce2948d670181ff>,
expected: <3b0e3ff57a8ea1ae614c6b648999be35838c0edbd24a2c2e18303ad135ac43b9>,
 dropping connection
2014-Dec-31 21:59:54.388299 [P2P4]ERROR ../../src/cryptonote_protocol/cryptonote_protocol_handler.inl:469 [69.60.113.24:35688 INC]Failed to handle NOTIFY_REQUEST_CHAIN.
2014-Dec-31 21:59:54.479409 [P2P4]
**********************************************************************
The daemon will start synchronizing with the network. It may take up to several hours.

You can set the level of process detailization* through "set_log <level>" command*, where <level> is between 0 (no details) and 4 (very verbose).

Use "help" command to see the list of available commands.

Note: in case you need to interrupt the process, use "exit" command. Otherwise, the current progress won't be saved.

Note: in case you need to interrupt the process, use "exit" command. Otherwise, the current progress won't be saved.
**********************************************************************
2014-Dec-31 21:59:54.859333 [P2P9][54.87.190.112:36708 INC]Sync data returned unknown top block: 1 -> 354 [353 blocks (0 days) behind]
SYNCHRONIZATION started
2014-Dec-31 21:59:54.984036 [P2P2]ERROR ../../src/cryptonote_core/blockchain_storage.cpp:1154 Client sent wrong NOTIFY_REQUEST_CHAIN: genesis block missmatch:
id: <80e28ab82d17e61319309c7525d2f76a78731d0c6099b646bce2948d670181ff>,
expected: <3b0e3ff57a8ea1ae614c6b648999be35838c0edbd24a2c2e18303ad135ac43b9>,
 dropping connection
2014-Dec-31 21:59:54.984729 [P2P2]ERROR ../../src/cryptonote_protocol/cryptonote_protocol_handler.inl:469 [54.87.190.112:36708 INC]Failed to handle NOTIFY_REQUEST_CHAIN.
2014-Dec-31 21:59:57.798558 [P2P7][69.60.113.25:6180 OUT]Sync data returned unknown top block: 1 -> 354 [353 blocks (0 days) behind]
SYNCHRONIZATION started
2014-Dec-31 21:59:57.802376 [P2P5]
**********************************************************************
You are now synchronized with the network. You may now start simplewallet.

Please note, that the blockchain will be saved only after you quit the daemon with "exit" command or if you use "save" command.
Otherwise, you will possibly need to synchronize the blockchain again.

Use "help" command to see the list of available commands.
**********************************************************************
2014-Dec-31 21:59:57.803938 [P2P5]Mining has started with 1 threads, good luck!
2014-Dec-31 21:59:57.803968 Miner thread was started

2014-Dec-31 21:59:57.804117 [miner 0]Using global boulderhash state
2014-Dec-31 21:59:57.804525 [P2P5][(localIP):52689 INC] SYNCHRONIZED OK
2014-Dec-31 21:59:57.804870 [P2P5][sock 19] Some problems at write: Broken pipe:32
2014-Dec-31 21:59:57.804598 [P2P8]ERROR ../../src/p2p/net_node.inl:599 Failed to get random peer from peerlist(white:0)
2014-Dec-31 21:59:57.836488 [P2P2]ERROR ../../src/cryptonote_core/blockchain_storage.cpp:1154 Client sent wrong NOTIFY_REQUEST_CHAIN: genesis block missmatch:
id: <80e28ab82d17e61319309c7525d2f76a78731d0c6099b646bce2948d670181ff>,
expected: <3b0e3ff57a8ea1ae614c6b648999be35838c0edbd24a2c2e18303ad135ac43b9>,
 dropping connection
2014-Dec-31 21:59:57.842885 [P2P2]ERROR ../../src/cryptonote_protocol/cryptonote_protocol_handler.inl:469 [69.60.113.25:6180 OUT]Failed to handle NOTIFY_REQUEST_CHAIN.
2014-Dec-31 21:59:59.264618 [miner 0]Found block for difficulty: 1
Hash was: <c6c499cfa060bb4a5baa602febe79eb97bc790e23407b1fb0f41a9041d669ede>

The client then begins forking itself, mining on the bad chain:


2014-Dec-31 22:00:02.208731 [miner 0]Found block for difficulty: 1
Hash was: <ac25dc49324f5d637c42f20c00827cc59ffe5d727a826da03589f05528dc7d5c>

2014-Dec-31 22:00:05.305178 [miner 0]Found block for difficulty: 4
Hash was: <8b9ca84591ac2e4c7020eb36dd339f58afd01204e55e7104b9cad88445507915>

2014-Dec-31 22:00:14.229253 [miner 0]Found block for difficulty: 10
Hash was: <ccbdcd3105b26a29aa47f173c46827369c8203d02eb4513ec4fdf9d65ba51716>

2014-Dec-31 22:01:09.452519 [miner 0]Found block for difficulty: 20
Hash was: <fd59fb83d67cb04ee08873dbb27990aee01dcc8e910c1a5de0293b9520dc3504>

2014-Dec-31 22:01:18.398278 [miner 0]Found block for difficulty: 35
Hash was: <716eaf8c342b3b8d58827a744aaa9e3bdcd23f422de80b61059e4d95f3059a06>

[bathrobehero]

Boulderhash is a new mining algorithm requiring 13 GB RAM, nearly eliminating all possible zombie (botnet controlled) computers from mining.

Refreshing idea, but I'm pretty sure most people who have 16 GB or more memory, they actually need it and use it. I for one won't be holding 13 GB of RAM hostage for a coin. On the other hand server owners with massive amounts of memory have a huge advantage. And you can rent servers with like 192 GB memory. You mentioned heavily weighted distribution of coins when in reality your distribution method is really poor as the coins wil end up going to a small group of people.

[pantheist]

Boulderhash is a new mining algorithm requiring 13 GB RAM, nearly eliminating all possible zombie (botnet controlled) computers from mining.

Refreshing idea, but I'm pretty sure most people who have 16 GB or more memory, they actually need it and use it. I for one won't be holding 13 GB of RAM hostage for a coin.

+1

[XPB]

Boulderhash is a new mining algorithm requiring 13 GB RAM, nearly eliminating all possible zombie (botnet controlled) computers from mining.

Refreshing idea, but I'm pretty sure most people who have 16 GB or more memory, they actually need it and use it. I for one won't be holding 13 GB of RAM hostage for a coin. On the other hand server owners with massive amounts of memory have a huge advantage. And you can rent servers with like 192 GB memory. You mentioned heavily weighted distribution of coins when in reality your distribution method is really poor as the coins wil end up going to a small group of people.

The benefit for getting specialized hardware with specific specs is significantly less than any other hashing algorithm that allow for ASICS or GPUs.  This is as fair as it gets.

[Vorksholk]

Ahh, figured out my problem. The information in OP is outdated for the command-line arguments to simplewallet. Make sure you use the ones from the configuration file instead.

For anyone curious, here is how you should be launching simplewallet:
./simplewallet --genesis-nonce-string "31/Dec/2014 OPEN NASDAQ 4790.53 DAX 9883.10 DOW 17987.66" --genesis-timestamp 1420044761 --genesis-coinbase-hex 010a01ff0000210179e231c0574796ecc198e05afaecd3aea2d9a84fa6c51088eb75130c4eb4da7 2 --genesis-id-hash-hex 80e28ab82d17e61319309c7525d2f76a78731d0c6099b646bce2948d670181ff --genesis-work-hash-hex 9edc9d0ddd03c534300c9f4647a21998af9c0a4cdb9786c9f9b1f10095f5bacf --genesis-work-hash-signature 9578dd84ed25b51fcde0b87505cf94ebf2b4e4ed5fc28c1a05650a06b80bde040cfaf44a7f32ef4 15f1e8bd016ce012fb44f5bc1e3aa3f5f41600235a7417f01

(Note the different values for all of the above arguments. It appears the dev copied and pasted ones he was using on a test from the 30th instead of the 31st.)

Edit: On second look, if you generated a wallet using the data in OP, you will probably have to re-create a new wallet with the above correct data.

The show_hr command doesn't appear to work inside the daemon.

[jones techbit]

waiting for fair launch

[SalimNagamato]

i got few blocks before noticing the mistake in OP
but probably not valid because used address generated by the wrong simplewallet command.. ?
it is possible to still use it ? can export private key and use in new wallet?

[XPB]

i got few blocks before noticing the mistake in OP
but probably not valid because used address generated by the wrong simplewallet command.. ?
it is possible to still use it ? can export private key and use in new wallet?

If you were mining on the wrong fork, you wont have coins on the current chain.  This is precisely why the rewards at launch start so low, 0.1% of what they will be in three weeks.  Thank you Vorksholk for correcting the config file.

[SalimNagamato]

i got few blocks before noticing the mistake in OP
but probably not valid because used address generated by the wrong simplewallet command.. ?
it is possible to still use it ? can export private key and use in new wallet?

If you were mining on the wrong fork, it won't work on the current chain.  This is precisely why the rewards at launch start so low, 0.1% of what they will be in three weeks.  Thank you Vorksholk for correcting that.

i wasn't mining on wrong fork (.conf file was correct), just generated wallet using wrong genesis block data
i can see the very low block reward... so maybe instamine not that bad

[CowboyKiller]

This coin is designed for a very tiny fraction of the altcoin community. If your goal was to make it the most exclusive coin yet, kudos. If your goal was fairness, back to the drawing board.

[Vorksholk]

2) Distribution of coins (active)

It is very common in the launch of a new cryptocurrency the distribution algorithm heavily is weighted towards the very early adopters.  Such distribution is designed to give a massive advantage to people who are fully prepared to mine at launch, with a very large difference shortly after sometimes a few days later.  If the point of mining is to both secure the network and fairly distribute coins a gradual build up of rewards makes more sense, with no drop off in mining rewards.  At a standard block reward of 300, at launch each block will reward 0.3 coins leading up to 3, 30, and finally the standard reward of 300 which will be the standard unchanging reward from that point.  It will take approximately 3 weeks for the block reward of 300 to be reached.

Right now, blocks appear to be worth far less than 0.3 coins.

Height 391, transaction <9ea334b55889dbbbb7124311acfdc867727db16c5a3bb92a6c44db10d7c4dc69>, received 0.00387897
Height 393, transaction <d2d114e4133b67bbf2f5866d400358928595a10abfe5434f154def91fd9456b9>, received 0.00389881
Height 395, transaction <152131f947dd47b6329f4d504912db4ef04ba3a24e95b64c0afcff99f949118a>, received 0.00391865
Height 397, transaction <f5bb12afea047a685a653ce298ab13a55e2c506eb4cc0ad429a8723d9a991323>, received 0.00393850
Height 401, transaction <2f2f8b9c555047e5609a33d6c248aef6785b65ced1e0168318d2ab3b807ceb10>, received 0.00397818
Height 403, transaction <957f5675810bc3a6f99b9d8bf5c001562961815c3dc64049321941face17d3f3>, received 0.00399802
Height 404, transaction <4d988fc591722663d524cf53985f6195e8edb5a93692b449659a09db95ed2f46>, received 0.00400794
Height 407, transaction <3885c1338fe7f85b60672832d1ce18b9433b9c633007116b5691859916ab35c2>, received 0.00403770
Height 408, transaction <d7ca37585fc2d4e8060fffddf2a8f416d153ffd9215cba0d33a74d3c34da24b8>, received 0.00404762
Height 409, transaction <d14ad19296315cff93faa5f4da78a9b297fb8e43c75810595eea8ee17af4c621>, received 0.00405754
Height 410, transaction <6805808518bfc30778bee2b3aa0a3817ef08224cd91b475768cf8a0c7a89bda0>, received 0.00406746
However, the reward is certainly increasing, it would appear at a rate of 0.00000992 XPB per block.

Additionally, it appears this block reward increase rate has been constant since launch:

Code:

print_block 1
block_id: <e7022558a1db08840eaeefdabc78c7a874caa3c22c773636643abc1acc572f14>
{
  "major_version": 1,
  "minor_version": 0,
  "timestamp": 1420045059,
  "prev_id": "80e28ab82d17e61319309c7525d2f76a78731d0c6099b646bce2948d670181ff",
  "nonce": 2560968748,
  "miner_tx": {
    "version": 1,
    "unlock_time": 11,
    "vin": [ {
        "gen": {
          "height": 1
        }
      }
    ],
    [b]"vout": [ {
        "amount": 993,
        "target": {
          "key": "b10f2823cb33bc86c1a5d6f9db7db5b35935eff73797ec61b81b80678cc63652"
        }[/b]
      }
    ],
    "extra": [ 1, 18, 123, 185, 12, 142, 71, 242, 140, 202, 226, 46, 174, 141, 109, 250, 144, 16, 177, 225, 217, 65, 19, 155, 171, 225, 54, 2, 144, 249, 113, 45, 180
    ],
    "signatures": [ ]
  },
  "tx_hashes": [ ]
}

Those are atomic units, so that would be a block reward of 0.00000993.

[bitcoin1992]

could anyone tell me how to solo?

[XPB]

Height 391, transaction <9ea334b55889dbbbb7124311acfdc867727db16c5a3bb92a6c44db10d7c4dc69>, received 0.00387897
Height 393, transaction <d2d114e4133b67bbf2f5866d400358928595a10abfe5434f154def91fd9456b9>, received 0.00389881
Height 395, transaction <152131f947dd47b6329f4d504912db4ef04ba3a24e95b64c0afcff99f949118a>, received 0.00391865
Height 397, transaction <f5bb12afea047a685a653ce298ab13a55e2c506eb4cc0ad429a8723d9a991323>, received 0.00393850
Height 401, transaction <2f2f8b9c555047e5609a33d6c248aef6785b65ced1e0168318d2ab3b807ceb10>, received 0.00397818
Height 403, transaction <957f5675810bc3a6f99b9d8bf5c001562961815c3dc64049321941face17d3f3>, received 0.00399802
Height 404, transaction <4d988fc591722663d524cf53985f6195e8edb5a93692b449659a09db95ed2f46>, received 0.00400794
Height 407, transaction <3885c1338fe7f85b60672832d1ce18b9433b9c633007116b5691859916ab35c2>, received 0.00403770
Height 408, transaction <d7ca37585fc2d4e8060fffddf2a8f416d153ffd9215cba0d33a74d3c34da24b8>, received 0.00404762
Height 409, transaction <d14ad19296315cff93faa5f4da78a9b297fb8e43c75810595eea8ee17af4c621>, received 0.00405754
Height 410, transaction <6805808518bfc30778bee2b3aa0a3817ef08224cd91b475768cf8a0c7a89bda0>, received 0.00406746
However, the reward is certainly increasing, it would appear at a rate of 0.00000992 XPB per block.

Additionally, it appears this block reward increase rate has been constant since launch:

It builds up to 300 XPB per block.  At the moment the rewards are very trivial.

[Vorksholk]

could anyone tell me how to solo?

Sure can.

Download pebblecoind and simplewallet from the dropbox links above.

Assuming you are on a Linux box, you are going to want to run simplewallet first to get an address:
(And remember, if you are on a headless box, you might consider running this stuff in screen sessions in case your SSH connection dies)

Code:

chmod a+x simplewallet
./simplewallet --genesis-nonce-string "31/Dec/2014 OPEN NASDAQ 4790.53 DAX 9883.10 DOW 17987.66" --genesis-timestamp 1420044761 --genesis-coinbase-hex 010a01ff0000210179e231c0574796ecc198e05afaecd3aea2d9a84fa6c51088eb75130c4eb4da72 --genesis-id-hash-hex 80e28ab82d17e61319309c7525d2f76a78731d0c6099b646bce2948d670181ff --genesis-work-hash-hex 9edc9d0ddd03c534300c9f4647a21998af9c0a4cdb9786c9f9b1f10095f5bacf --genesis-work-hash-signature 9578dd84ed25b51fcde0b87505cf94ebf2b4e4ed5fc28c1a05650a06b80bde040cfaf44a7f32ef415f1e8bd016ce012fb44f5bc1e3aa3f5f41600235a7417f01

Now, enter a passphrase, and copy that wallet address shown.

Now you are going to want to run pebblecoind to let it sync with the network. This is the daemon application, it handles all the heavy-lifting of the network, including mining.

Here's how you do that:

Code:

chmod a+x pebblecoind

Then create a config folder, let's call it ~/pebblecoin_data
Then create a file inside of that folder, called pebblecoin.conf with the following contents:

Code:

#genesis-nonce-string=31/Dec/2014 OPEN NASDAQ 4790.53 DAX 9883.10 DOW 17987.66
#genesis-timestamp=1420044761
#genesis-coinbase-hex=010a01ff0000210179e231c0574796ecc198e05afaecd3aea2d9a84fa6c51088eb75130c4eb4da72
#genesis-id-hash-hex=80e28ab82d17e61319309c7525d2f76a78731d0c6099b646bce2948d670181ff
#genesis-work-hash-hex=9edc9d0ddd03c534300c9f4647a21998af9c0a4cdb9786c9f9b1f10095f5bacf
#genesis-work-hash-signature-hex=9578dd84ed25b51fcde0b87505cf94ebf2b4e4ed5fc28c1a05650a06b80bde040cfaf44a7f32ef415f1e8bd016ce012fb44f5bc1e3aa3f5f41600235a7417f01

##seed nodes
add-peer=69.60.113.23:6180
add-peer=69.60.113.24:6180
add-peer=69.60.113.25:6180
add-peer=69.60.112.164:6180
add-peer=69.60.112.169:6180

##uncomment to start mining, replace address with your wallet address
enable-boulderhash=1
start-mining=[b]ENTERYOURADDRESSHERE[/b] (What you copied when you ran simplewallet)
mining-threads=1

##uncomment to verify proof of work hashes yourself, enable-boulderhash must be on:
disable-signed-hashes=1

(Make sure you have 13GB of available RAM). If you have more than 13GB, you can set the mining-threads=# to a higher number. For example, to use 26GB of RAM, set it to 2. Not sure if there is any performance increase from running multiple threads, as one mining thread seems to utilize all cores near 100%, however I set mine as high as possible just in case.

Now, you are going to want to run the daemon. Since you have the genesis block data in your conf file, you shouldn't need the command line arguments. However, we can supply them to be safe:

Code:

./pebblecoind --data-dir ~/pebblecoin_data/ --genesis-nonce-string "31/Dec/2014 OPEN NASDAQ 4790.53 DAX 9883.10 DOW 17987.66" --genesis-timestamp 1420044761 --genesis-coinbase-hex 010a01ff0000210179e231c0574796ecc198e05afaecd3aea2d9a84fa6c51088eb75130c4eb4da72 --genesis-id-hash-hex 80e28ab82d17e61319309c7525d2f76a78731d0c6099b646bce2948d670181ff --genesis-work-hash-hex 9edc9d0ddd03c534300c9f4647a21998af9c0a4cdb9786c9f9b1f10095f5bacf --genesis-work-hash-signature 9578dd84ed25b51fcde0b87505cf94ebf2b4e4ed5fc28c1a05650a06b80bde040cfaf44a7f32ef415f1e8bd016ce012fb44f5bc1e3aa3f5f41600235a7417f01

Mining should start automatically, but you can check htop to make sure it is mining. The above config file will force your client to verify each block, but that seemed to work well for me. If it is too slow, you can comment the line disable-signed-hashes=1 in your config file, and relaunch the daemon.

From here, you can interface directly with the wallet. Type refresh to see if you got any coins. Mined blocks will show up in the daemon like so:

Code:

2015-Jan-01 06:40:03.780106 [miner 4]Found block for difficulty: 391
Hash was: <40630dcba9fc8ec911b10b2b945aee1e2ef9f02a89051e360010151df5602100>

However the refresh command will tell you how many coins you got for that block.

[XPB]

This coin is designed for a very tiny fraction of the altcoin community. If your goal was to make it the most exclusive coin yet, kudos. If your goal was fairness, back to the drawing board.

At the moment, it takes some annoyance to setup, mine and use.  In a few weeks time there will be a download and run GUI with a mining pool setup.  It should all be done by the time block rewards hit 300 XPB/block.  What's going on now is somewhat of a test phase, although there are real XPB on block rewards .. just not very much.  What you mentioned is exactly the problem with *all* current cryptonote coins, and the reason why despite it being superior technology nobody uses it and exactly what I intend to change with XPB.  Adding a GUI is the first in very many steps to a cryptonote coin more usable and more widespread.