I want to figure out why it is not switching to main chain.
Maybe problem on firewall I guess no since handshake is ok. |
|
|
|
Dev hold 10% of coins?
No. The miners can chose to give 1% of the mined coins or not to the devs. owners of
122.117.207.143
and
117.131.169.12
please PM me ASAP.
Did we find the two forkers ? We found a bug i think. Just want to help with that, they wasting machine time. |
|
|
|
So chain has been forked.  How can I know if I am mining in the correct chain? Chain will not be forked, i've pushed checkpoins, so don't be afraid. There are two machines which works for nothing by mining alternative chain with low difficulty(each machine on it's own chain). I want to figure out why it is not switching to main chain. I've tried to start mine from first block and then turn back into main network - it's switchched ok to main chain. |
|
|
|
|
owners of
122.117.207.143
and
117.131.169.12
please PM me ASAP.
|
|
|
|
|
I see someone is mining alternative chain, bad idea because today i'll release checkpoints.
Or may be it happend because seed nodes was offline some time.
|
|
|
|
Can't sync/download the blockchain. Seed peers all fail and then failed handshakes.. Any ideas?
Seed nodes fixed. |
|
|
|
Hey guys,
What kind of CPUs do you use to mine BBR? i5, i7 ...? It looks like that core i5 is unable to solve blocks. My friend has a core i7. He solved 2 blocks at 200k for 3 days. My core i5 PCs yield 340k each but solves no block for 4 days.
CPU is not matter. Hashrate is only one significant indicator. Send me your address to PM. |
|
|
|
|
Good news!
Added more graphs:
1. Estimated network hashrate
2. Scratchpad size
3. alias amount (not very important yeah)
check this out: url=http://boolberry.com/state.html]state[/url] page.
Updated with new build part of the network (about 60 machines). If everything will be ok, i'll ask you all to update tomorrow.
Working on solving problem whit starting connection, seems that something wrong with async connection function.
|
|
|
|
How does this compare against MRO specifically?
MRO is the same as bytecoin(except emission curve), see comparsion in starter topic or on website. |
|
|
|
DarkNote is a very bad name actually. DarkCoin is already a bad name. 2 reasons:
+ Confused with DarkCoin. Make no distinction between 2 brands
+ Dark- makes a bad impression about the nature of the coin, making it bad in the eye of regulators and people in the clearnet.
agree |
|
|
|
hr: 40673
2014-May-23 19:30:36.469671 [P2P5]ERROR /Users/dinhpham/coins/boolberry/src/currency_core/tx_pool.cpp:70[bool currency::tx_memory_pool::add_tx(const currency::transaction &, const crypto::hash &, size_t, currency::tx_verification_context &, bool)]Transaction with id= <cce301d40ab4db52d51393fbf32141c7b8cd6511e5622456d6ce094921a1f7de> used already spent key images
2014-May-23 19:30:36.470473 [P2P5]Transaction verification failed: <cce301d40ab4db52d51393fbf32141c7b8cd6511e5622456d6ce094921a1f7de>
2014-May-23 19:30:36.470857 [P2P5][203.195.129.162:10101 OUT]Tx verification failed, dropping connection
2014-May-23 19:30:36.955861 [P2P5]ERROR /Users/dinhpham/coins/boolberry/src/currency_core/tx_pool.cpp:70[bool currency::tx_memory_pool::add_tx(const currency::transaction &, const crypto::hash &, size_t, currency::tx_verification_context &, bool)]Transaction with id= <cce301d40ab4db52d51393fbf32141c7b8cd6511e5622456d6ce094921a1f7de> used already spent key images
2014-May-23 19:30:36.956054 [P2P5]Transaction verification failed: <cce301d40ab4db52d51393fbf32141c7b8cd6511e5622456d6ce094921a1f7de>
2014-May-23 19:30:36.956151 [P2P5][116.254.199.48:10101 OUT]Tx verification failed, dropping connection
2014-May-23 19:30:36.975805 [P2P8]ERROR /Users/dinhpham/coins/boolberry/src/currency_core/tx_pool.cpp:70[bool currency::tx_memory_pool::add_tx(const currency::transaction &, const crypto::hash &, size_t, currency::tx_verification_context &, bool)]Transaction with id= <cce301d40ab4db52d51393fbf32141c7b8cd6511e5622456d6ce094921a1f7de> used already spent key images
2014-May-23 19:30:36.976222 [P2P8]Transaction verification failed: <cce301d40ab4db52d51393fbf32141c7b8cd6511e5622456d6ce094921a1f7de>
2014-May-23 19:30:36.976333 [P2P8][59.127.188.27:10101 OUT]Tx verification failed, dropping connection
2014-May-23 19:30:37.122507 [P2P5]ERROR /Users/dinhpham/coins/boolberry/src/currency_core/tx_pool.cpp:70[bool currency::tx_memory_pool::add_tx(const currency::transaction &, const crypto::hash &, size_t, currency::tx_verification_context &, bool)]Transaction with id= <cce301d40ab4db52d51393fbf32141c7b8cd6511e5622456d6ce094921a1f7de> used already spent key images
2014-May-23 19:30:37.122711 [P2P5]Transaction verification failed: <cce301d40ab4db52d51393fbf32141c7b8cd6511e5622456d6ce094921a1f7de>
2014-May-23 19:30:37.122820 [P2P5][124.119.29.186:10101 OUT]Tx verification failed, dropping connection
2014-May-23 19:30:37.289487 [P2P5]ERROR /Users/dinhpham/coins/boolberry/src/currency_core/tx_pool.cpp:70[bool currency::tx_memory_pool::add_tx(const currency::transaction &, const crypto::hash &, size_t, currency::tx_verification_context &, bool)]Transaction with id= <cce301d40ab4db52d51393fbf32141c7b8cd6511e5622456d6ce094921a1f7de> used already spent key images
2014-May-23 19:30:37.289684 [P2P5]Transaction verification failed: <cce301d40ab4db52d51393fbf32141c7b8cd6511e5622456d6ce094921a1f7de>
2014-May-23 19:30:37.289846 [P2P5][114.251.77.218:10101 OUT]Tx verification failed, dropping connection
I guess this problem will be solved after network update. |
|
|
|
My total HR is about 900kh/s but I can not find any block for 3 days. Pool is needed or mining is just a waste of power
Sorry about this amigo. Pool will appear sooner or later (hope sooner). |
|
|
|
now with shared scratchpad miner uses locking (pthread), check how many % of CPU time is spent in pthread_mutex_lock/unlock.
With x86_64 Linux 3.14 and glibc-2.18 those two functions consume 0.7%.
Does boost shared/exclusive lock always used mutex_lock/unlock? As i traced it on windows in debuger - if scratchpad is not in exclusive access - for shared access it makes only atomic operations (interlocked). Am i wrong ? |
|
|
|
Friends, thank you for trying to help us! I read this thread every day, and hope we will find good name. I just want to remind you that name have to be unique, this means that when you google it you will not get a lot of results, just as example: Aura [AURA]
Nube [NUBE]
Bruma [BRU]
Aura - 81 000000 results Nube - 21 000000 results Bruma - 28 000000 results Please, keep it in the mind. May be we can move focus from anonymity and from coins to something neutral, something pretty far from currency. Uncommon flower may be (isn't it nice to send each other flowers instead of coins ?  ) As for me - the best currency name after bitcoin is ripple. I think it well done. Peace! |
|
|
|
I'm adding 25 BBR to the bounty. Hopefully we find a great name. Thank you! |
|
|
|
Good news! As you may know (some people definitely know) that we had some problems with transactions for big amounts. I hit this problem with 3 different points: 1. I set up transaction pool to have live-time for each transaction that received (24 hours). Even if you sent some transaction that could not be included in blocktemplate, this transaction will be removed from tx pools after 24 hours, and you will be able to try again with you wallet. 2. I set up wallet to check transaction size befor sending it to the network, and if transaction size big enough to have problems - transaction is canceled and notice displayed. 3. Finally, I rewrote wallet outs collecting with new size-effective policy. I've tested it in testnetwork - now transaction for 1000BBR have only 5kbytes, it's about 7-8 times less than it was, and it's ok to send. Hope you will enjoy it. I've published new binaries and sources, but i think we have to test this version for one or two days, after that, if everything is ok, i'll ask miners to move on this new version and push signed alert to the network . And another good news is that testnet is launched again, if you want to make experiments - welcome. Please remove old blockchain for test net before start. People who have stucked transactions in pools: This update will release your money, but only after biggest part of the network will move to this new version. Just wait for while, i'll support you with this issue until you we completely solve it. Next problem to solve: Failed to get remote endpoint PS: MacOS build will be tomorrow. I'll answer to posts later. |
|
|
|
I just updated from source and lost roughly a 1/3 of my hashing power. What's going on cryto?
Someone else seen this behavior? I've tested on corei5 it was the same rate. Could you please compare hashrate of two versions right now, on current height? !!Hashrate on all machines is going to be decreased, due to growing of scratchpad!! |
|
|
|
zoidberg, is only the emission rate of the dev bounty controlled by miners, or is the amount of the dev bounty controlled by miners? i.e. is it certain that the devs will receive 1% of final supply?
Yes. 1% of emission is reserved for devs. |
|
|
|
I just tried to transfer coins to Surfer43 and I'm now getting this error:
Wallet:
[wallet 1GJ86N]: transfer 0 @surfer43 100
Error: transaction <80a6238162cf44a133ed7ebe19d6430302571adbe5ebe5096189c4d87f1495b0> was rejected by daemon with status "Failed"
Daemon:
2014-May-22 05:29:04.462250 [RPC1]ERROR /home/ubuntu/boolberry/src/currency_core/tx_pool.cpp:70[bool currency::tx_memory_pool::add_tx(const currency::transaction&, const crypto::hash&, size_t, currency::tx_verification_context&, bool)]Transaction with id= <80a6238162cf44a133ed7ebe19d6430302571adbe5ebe5096189c4d87f1495b0> used already spent key images
2014-May-22 05:29:04.462392 [RPC1]Transaction verification failed: <80a6238162cf44a133ed7ebe19d6430302571adbe5ebe5096189c4d87f1495b0>
I guess it happend because wallet was hard-closed without typing exit command. If your previous transaction commited to blockchain, you may just remove wallet-data file and reopen your wallet-keys file, all gonna be alright. But if your prev transaction stuck in tx_pool - it's not good. I'm going to make fix with tx_pool's transactions live time, but you have to wait for a while. This issue in all cryptonote family is a result of bad balanced CURRENCY_BLOCK_GRANTED_FULL_REWARD_ZONE constant. Guys, don't send big amounts. Recomend you to send max 100BBR until we fix wallet |
|
|
|
Some fresh news, to keep all informed. 1. Fixed bug in displaying hashrate while mining is turned off 2. Implemented stricted alias check in wallet ( http://boolberry.com/howto.html#aliases) 3. Updated miner to work all threads on one shared scratchpad (begins to make sense in the nearest future) 4. Fixed problem with dead connecions (it was seen on this graph)  Now it's fine. And also it could be seen as this problem: I get a error on Ubuntu 13.10 in the daemon 2014-Mai-21 23:28:16.33016 [P2P6][sock 94] Some problems at write: Broken pipe:32 Let me know if this will apear again with new version. 6. Problem with stuck transactions in tx pool investigated, not solved yet. I wrote some recomendations how to avoid this problem. All the bests! |
|
|
|
|
Show Posts
