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

XPB

full member

Activity: 132

Merit: 100

Quote from: SalimNagamato on January 01, 2015, 02:13:56 AM

Quote from: XPB on January 01, 2015, 02:08:51 AM

Quote from: SalimNagamato on January 01, 2015, 02:06:33 AM

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

In Cryptonote, the wallet is actually two files. Say the wallet is called "mywallet", it will generate a file "mywallet.keys" and another file "mywallet". The "mywallet" file is just a cache, if you delete this file (but not the keys file) and re-open the wallet it will reindex and you should be able to access your coins.

Vorksholk

legendary

Activity: 1713

Merit: 1029

Quote from: MisO69 on January 01, 2015, 01:19:58 PM

Anyone get simplewallet to work on Win64?

I get this after issuing the command as instructed. Using both the devs and Vorksholk's code.. The daemon syncs up fine.

pebblecoin wallet v0.1.0.4()
2015-Jan-01 12:15:12.016115 Genesis block nonce is: 1593709698
2015-Jan-01 12:15:12.016115 Provided incorrect block id hash hex. Given 80e28ab8
2d17e61319309c7525d2f76a78731d0c6099b646bce2948d670181ff, but block hashed to 3f
411af6c3e3add0d8ceb5ce28e8c69673941c7a4be9b3224514bf0c8c07d706

Try creating a new wallet, I had the same problem when I was trying to use a wallet that I generated with the wrong genesis information.

MisO69

legendary

Activity: 1946

Merit: 1005

My mule don't like people laughing

Anyone get simplewallet to work on Win64?

I get this after issuing the command as instructed. Using both the devs and Vorksholk's code.. The daemon syncs up fine.

pebblecoin wallet v0.1.0.4()
2015-Jan-01 12:15:12.016115 Genesis block nonce is: 1593709698
2015-Jan-01 12:15:12.016115 Provided incorrect block id hash hex. Given 80e28ab8
2d17e61319309c7525d2f76a78731d0c6099b646bce2948d670181ff, but block hashed to 3f
411af6c3e3add0d8ceb5ce28e8c69673941c7a4be9b3224514bf0c8c07d706

XPB

full member

Activity: 132

Merit: 100

Quote from: Shadow_Runner on January 01, 2015, 05:56:39 AM

Why cryptonote coins so unstable? And when it get GUI at least?

GUI by 18 Jan, still testing. Will be the first cryptonote coin with a proper GUI.

YesOrNo

full member

Activity: 143

Merit: 100

Hello world
Is it really safe. Virustotal 3/52

https://www.virustotal.com/pl/file/eca44bd3653947f277d10ac578c5d2d91ddef9adb2c17b173224a8d85f88983d/analysis/1420113937/

Shadow_Runner

hero member

Activity: 574

Merit: 500

Why cryptonote coins so unstable? And when it get GUI at least?

bathrobehero

legendary

Activity: 2002

Merit: 1051

ICO? Not even once.

Quote from: XPB on January 01, 2015, 02:51:40 AM

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.

How could it be more widespread when it starts with a poor distribution method? I'm not saying the memory requirements are bad but no GUI is going to help distribution when the vast majority of users can't even participate in the distribution. The point of good coin distribution is to hit as many people as possible and you act like this coin have a good distribution method when in fact it is quite the opposite.

Sure, you can market it and add utility to the coin later down the line but that will be offset by the fact that all the coins will belong to a few individuals.

PeaMine

hero member

Activity: 979

Merit: 510

15-Jan-01 08:32:33.343682 Error: refresh failed: no connection to daemon. Please, make sure daemon is running. Blocks received: 0
Error: refresh failed: no connection to daemon. Please, make sure daemon is running. Blocks received: 0

daemon is running and synced, but mining, can wallet not connect?

z38630610

legendary

Activity: 1050

Merit: 1000

how to work for windows7 64bit ,dev

dev why ?help no link

kahir

legendary

Activity: 1050

Merit: 1000

okay i got my wallet to work after 1 hour of trying those codes Cheesy

...

also i like the intensive memory usage

XPB

full member

Activity: 132

Merit: 100

Quote from: CowboyKiller on January 01, 2015, 02:17:29 AM

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.

Vorksholk

legendary

Activity: 1713

Merit: 1029

Quote from: bitcoin1992 on January 01, 2015, 02:32:21 AM

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

full member

Activity: 132

Merit: 100

Quote

Height 391, transaction <9ea334b55889dbbbb7124311acfdc867727db16c5a3bb92a6c44db10d7c4dc69>, received 0.00387897
Height 393, transaction , received 0.00389881
Height 395, transaction <152131f947dd47b6329f4d504912db4ef04ba3a24e95b64c0afcff99f949118a>, received 0.00391865
Height 397, transaction , 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 , received 0.00404762
Height 409, transaction , 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.

bitcoin1992

sr. member

Activity: 342

Merit: 250

could anyone tell me how to solo?

Vorksholk

legendary

Activity: 1713

Merit: 1029

Quote from: XPB on January 01, 2015, 12:16:11 AM

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 , received 0.00389881
Height 395, transaction <152131f947dd47b6329f4d504912db4ef04ba3a24e95b64c0afcff99f949118a>, received 0.00391865
Height 397, transaction , 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 , received 0.00404762
Height 409, transaction , 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: 
{
  "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.

CowboyKiller

sr. member

Activity: 463

Merit: 250

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.

SalimNagamato

legendary

Activity: 924

Merit: 1000

Quote from: XPB on January 01, 2015, 02:08:51 AM

Quote from: SalimNagamato on January 01, 2015, 02:06:33 AM

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

XPB

full member

Activity: 132

Merit: 100

Quote from: SalimNagamato on January 01, 2015, 02:06:33 AM

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

legendary

Activity: 924

Merit: 1000

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?

jones techbit

full member

Activity: 138

Merit: 100

waiting for fair launch

Topic: Pebblecoin (XPB) - FIRST DPOS CRYPTONOTE COIN LIVE - Qt Wallet GUI - v0.4.4.1 - page 33. (Read 56017 times)