Bitcoin Forum
June 21, 2024, 04:15:34 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1]
1  Local / Desenvolvimento & Discussões Técnicas / Re: reward de blocos altos - blockchain proprio on: February 19, 2018, 09:58:45 PM
coloquei o supply como

const uint64_t MONEY_SUPPLY                                  = (uint64_t)(-1);

na documentacao diz:

//TODO ((uint64_t)(-1)) equals to 18446744073709551616 coins
//TODO or you can define number explicitly UINT64_C(858986905600000000)
2  Local / Desenvolvimento & Discussões Técnicas / Re: reward de blocos altos - blockchain proprio on: February 18, 2018, 02:47:27 PM
vou colocar mais miners pra testar. valeu girino pela ajuda  Smiley
3  Local / Desenvolvimento & Discussões Técnicas / Re: reward de blocos altos - blockchain proprio on: February 18, 2018, 01:26:23 PM
mas será que todas as moedas começam com valores assim tão altos? olhando os forks da cryptonote (monero, bytecoin, aeon) vejo que os block rewards deles não são assim altos. pelo contrário.
a minha dúvida: será alguma config mesmo ou será simplesmente o fato de eu estar minerando sozinho logo no inicio?
4  Local / Desenvolvimento & Discussões Técnicas / reward de blocos altos - blockchain proprio on: February 17, 2018, 09:14:54 PM
fala galera
to desenvolvendo um blockchain proprio baseado no cryptonote e tenho notado um problema.

cada bloco descoberto na mineração (colocando so uma maquina minerando) ta rendendo um valor muito alto. queria que começasse baixo, com 1 moeda a cada bloco.

pra vocês terem uma idéia:

Height 1, transaction c9fc317310c43e624143e9236471ce331a3f1624be4fb221c6590d2895bc39cc, received 87960.88827904
Height 2, transaction ca19642fd2888fa43b7e17a2576cd802024019a2151e56a3985129e192cf401f, received 87960.84633602
Height 3, transaction cd5f5b454b9ceba6fc8d8250fd3bd5733f202a9191725df1f61231d7fb4f4a79, received 87960.80439301
Height 4, transaction 42cd4f2bd1e4b3e037092b752aee33580cb1f24c97fea1f218fb16f47801b29c, received 87960.76245003

available balance: 0.00000000, locked amount: 351843.30145810

na minha config de block reward, eu tenho a config:

const size_t   CRYPTONOTE_REWARD_BLOCKS_WINDOW               = 100;
const size_t   CRYPTONOTE_BLOCK_GRANTED_FULL_REWARD_ZONE     = 10000; //size of block (bytes) after which reward for b$
const size_t   CRYPTONOTE_COINBASE_BLOB_RESERVED_SIZE        = 600;



eu ja cheguei a colocar o CRYPTONOTE_BLOCK_GRANTED_FULL_REWARD_ZONE como 1, mas mesmo assim os valores ficam muito altos.

alguém tem idéia do que pode ser?

valeu!!

5  Other / Beginners & Help / public miner from a new coin on: February 13, 2018, 04:24:41 PM
hi guys,
I started my new cryptocurrency based on CryptoNote.
The daemon is running fine. But, I don't have seeds.
Wallet is ok. And, I can run miner in localhost.
But, when I try to miner remotly (from my pc)

>> Command I running in my blockchain:

mycurrencyd --allow-local-ip --seed-node 127.0.0.1:17236  --rpc-bind-ip 0.0.0.0

>> Command I running in my local pc:

./minerd -o my_ip:17236
[2018-02-13 13:22:04] Binding thread 0 to cpu 0
[2018-02-13 13:22:04] Binding thread 1 to cpu 1
[2018-02-13 13:22:04] Binding thread 2 to cpu 2
[2018-02-13 13:22:04] Binding thread 3 to cpu 3
[2018-02-13 13:22:04] Binding thread 4 to cpu 4
[2018-02-13 13:22:04] Binding thread 5 to cpu 5
[2018-02-13 13:22:04] Binding thread 6 to cpu 6
[2018-02-13 13:22:04] 8 miner threads started, using 'scrypt' algorithm.
[2018-02-13 13:22:04] Binding thread 7 to cpu 7
[2018-02-13 13:22:05] HTTP request failed: Recv failure: Connection reset by peer
[2018-02-13 13:22:05] json_rpc_call failed, retry after 30 seconds




Error receiveid in mymoneyd:
Exception in connectionHandler: Levin signature mismatch


Log when I started my moneyd:

11:21:51.856121 INFO Binding on 0.0.0.0:17236
11:21:51.856388 INFO Net service binded on 0.0.0.0:17236
11:21:51.856567 INFO Attempting to add IGD port mapping.
11:21:55.861582 INFO No IGD was found.
11:21:55.861778 INFO P2p server initialized OK
11:21:55.861928 INFO Initializing core...
11:21:55.862352 INFO Loading blockchain...
11:21:55.862584 WARNING No actual blockchain cache found, rebuilding internal structures...
11:21:55.862772 INFO Height 0 of 8
11:21:55.863421 INFO Rebuilding internal structures took: 0.000655607
11:21:55.863556 INFO Loading blockchain indices for BlockchainExplorer...
11:21:55.863729 WARNING No actual blockchain indices for BlockchainExplorer found, rebuilding...
11:21:55.863803 INFO Height 0 of 8
11:21:55.864093 INFO Rebuilding blockchain indices took: 0.000291316
11:21:55.864205 INFO Blockchain initialized. last block: 7, d0.h0.m48.s2 time ago, current difficulty: 5036
11:21:55.864271 INFO Core initialized OK
11:21:55.864480 INFO Starting core rpc server on address 0.0.0.0:18236
11:21:55.864660 INFO Core rpc server started ok
11:21:55.864774 INFO Starting p2p net loop...
11:21:55.864835 INFO Starting node_server
11:21:55.867140 INFO
11:21:55.867140 INFO **********************************************************************
11:21:55.867140 INFO You are now synchronized with the network. You may now start simplewallet.
11:21:55.867140 INFO
11:21:55.867140 INFO Please note, that the blockchain will be saved only after you quit the daemon with "exit" command or if you use "save" command.
11:21:55.867140 INFO Otherwise, you will possibly need to synchronize the blockchain again.
11:21:55.867140 INFO
11:21:55.867140 INFO Use "help" command to see the list of available commands.
11:21:55.867140 INFO **********************************************************************
11:21:55.868880 INFO
11:21:55.868880 INFO **********************************************************************
11:21:55.868880 INFO The daemon will start synchronizing with the network. It may take up to several hours.
11:21:55.868880 INFO
11:21:55.868880 INFO You can set the level of process detailization* through "set_log <level>" command*, where <level> is between 0 (no details) and 4 (very verbose).
11:21:55.868880 INFO
11:21:55.868880 INFO Use "help" command to see the list of available commands.
11:21:55.868880 INFO
11:21:55.868880 INFO Note: in case you need to interrupt the process, use "exit" command. Otherwise, the current progress won't be saved.
11:21:55.868880 INFO **********************************************************************
11:21:55.870415 WARNING [127.0.0.1:54697 INC] Exception in connectionHandler: TcpConnection::read




Pages: [1]
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!