Author

Topic: [BBR] Boolberry: Privacy and Security - Guaranteed Since 2014 - page 463. (Read 1210753 times)

legendary
Activity: 1106
Merit: 1000
Code:
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= used already spent key images
2014-May-23 19:30:36.470473 [P2P5]Transaction verification failed:
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= used already spent key images
2014-May-23 19:30:36.956054 [P2P5]Transaction verification failed:
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= used already spent key images
2014-May-23 19:30:36.976222 [P2P8]Transaction verification failed:
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= used already spent key images
2014-May-23 19:30:37.122711 [P2P5]Transaction verification failed:
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= used already spent key images
2014-May-23 19:30:37.289684 [P2P5]Transaction verification failed:
2014-May-23 19:30:37.289846 [P2P5][114.251.77.218:10101 OUT]Tx verification failed, dropping connection
legendary
Activity: 1106
Merit: 1000
Quote
2014-May-23 19:25:18.658142 [P2P7]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= <04e2d94d23074c600ae55dfd17d27c622d537c2b312edd23f08815e6ef6c6e00> used already spent key images
2014-May-23 19:25:18.658957 [P2P7]Transaction verification failed: <04e2d94d23074c600ae55dfd17d27c622d537c2b312edd23f08815e6ef6c6e00>
2014-May-23 19:25:18.659172 [P2P7][27.225.109.70:10101 OUT]Tx verification failed, dropping connection
2014-May-23 19:25:18.736169 [P2P3]Selected peer: 10482307931045703537 107.170.131.188:10101[white=0] last_seen: d5.h18.m23.s0
2014-May-23 19:25:18.736306 [P2P3]Connecting to 107.170.131.188:10101(white=0, last_seen: d5.h18.m23.s0)...
2014-May-23 19:25:18.787535 [P2P7]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= <04e2d94d23074c600ae55dfd17d27c622d537c2b312edd23f08815e6ef6c6e00> used already spent key images
2014-May-23 19:25:18.787723 [P2P7]Transaction verification failed: <04e2d94d23074c600ae55dfd17d27c622d537c2b312edd23f08815e6ef6c6e00>
2014-May-23 19:25:18.787825 [P2P7][203.195.129.166:10101 OUT]Tx verification failed, dropping connection
2014-May-23 19:25:18.932467 [P2P7]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= <04e2d94d23074c600ae55dfd17d27c622d537c2b312edd23f08815e6ef6c6e00> used already spent key images
2014-May-23 19:25:18.932663 [P2P7]Transaction verification failed: <04e2d94d23074c600ae55dfd17d27c622d537c2b312edd23f08815e6ef6c6e00>
2014-May-23 19:25:18.932767 [P2P7][128.199.246.36:10101 OUT]Tx verification failed, dropping connection
2014-May-23 19:25:18.941180 [P2P1]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= <04e2d94d23074c600ae55dfd17d27c622d537c2b312edd23f08815e6ef6c6e00> used already spent key images
2014-May-23 19:25:18.941372 [P2P1]Transaction verification failed: <04e2d94d23074c600ae55dfd17d27c622d537c2b312edd23f08815e6ef6c6e00>
2014-May-23 19:25:18.941472 [P2P1][107.170.193.84:10101 OUT]Tx verification failed, dropping connection
2014-May-23 19:25:19.045433 [P2P3]Connect failed to 107.170.131.188:10101
2014-May-23 19:25:19.045557 [P2P3]Selected peer: 16991166296079854261 203.195.129.162:10101[white=0] last_seen: d0.h14.m7.s4
2014-May-23 19:25:19.045640 [P2P3]Connecting to 203.195.129.162:10101(white=0, last_seen: d0.h14.m7.s4)...
hr: 78945
2014-May-23 19:25:19.314981 [P2P8][203.195.129.162:10101 OUT] COMMAND_HANDSHAKE INVOKED OK
2014-May-23 19:25:19.315151 [P2P3]Selected peer: 4965905881312989462 206.253.153.201:8080[white=0] last_seen: d4.h6.m37.s27
2014-May-23 19:25:19.315245 [P2P3]Connecting to 206.253.153.201:8080(white=0, last_seen: d4.h6.m37.s27)...
2014-May-23 19:25:19.607554 [P2P1]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= <04e2d94d23074c600ae55dfd17d27c622d537c2b312edd23f08815e6ef6c6e00> used already spent key images
2014-May-23 19:25:19.607745 [P2P1]Transaction verification failed: <04e2d94d23074c600ae55dfd17d27c622d537c2b312edd23f08815e6ef6c6e00>

Double spending?
sr. member
Activity: 336
Merit: 250
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 ?

Well you are using shared lock when doing only reads on m_scratchpad, and exclusive lock when writing to scratchpad, which is OK.
How many % of CPU time is spent in locking on Windows?
sr. member
Activity: 494
Merit: 250
wait for the pool
hero member
Activity: 938
Merit: 1001
Boolberry (HoneyPenny) Name Contest

Winning Name gets 125 150 BBR

surfer43 has added 25 BBR to the bounty!!

hero member
Activity: 976
Merit: 646
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).
hero member
Activity: 976
Merit: 646
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 ?
full member
Activity: 210
Merit: 100

Great work zoidberg! Thanks.
hero member
Activity: 976
Merit: 646
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:
Code:
Failed to get remote endpoint

PS: MacOS build will be tomorrow.

I'll answer to posts later.
sr. member
Activity: 280
Merit: 250
Who cares?
sr. member
Activity: 350
Merit: 250
Vires in Numeris
hey Crypto_Zoidberg I'm a fan of your project.
I think the cryptonote system addresses some of the major concerns of bitcoin and its derivatives. I also appreciate the changes to the cryptonote system found in your system. I've been wanting to mine since launch but the windows disadvantage has put me off permanently  Undecided

I do see the efficacy of the scratchpad based hashing in the future if it grows 90MB a year. For now this doesn't even really begin to tax GPU's with 6GB of ram. Basically with 6GB ram a GPU and a 90mb blockchain, you could perform 66 hashing functions concurrently yes? With a 180mb blockchain 33, with a 270mb blockchain 22, etc etc.

I also see how producing an ASIC with ever-increasing CPUs would be wasteful, as the amount of them that can actually work is wholly dependent on the RAM, the amount of these CPUs available to hash would be reduced by a large step each year. Basically, whats the point in having a ASIC that can perform 2000 hashing functions concurrently when you only have enough ram to do 20 or 30. However I don't believe that was indicated and explained in a clear and precise manner.

It does seem that in order to aid fairness, we should actually be focusing on producing a GPU miner now and as soon as possible. This would prevent a malicious coder creating one in secret and obtaining an unfair advantage.
Once we take that step to GPU mining, the playing field will be even and we know that ASICs will never be developed (as they are pointless in this scenario by design). Once that GPU miner is created the road will be paved and we can all be sure that no one has an unfair advantage.

As it stands, GPU mining will be more efficient than CPU mining for... 8.333 years.
This is a lot of time in the cryptocurrency world.

Until a GPU miner is created, we will always be wondering if someone else has one, and for good reason (66x efficiency? yes please!)

hero member
Activity: 543
Merit: 500
So,

I wanted to start mining, but simplewallet just pops up for a second and then closes.. what am I doing wrong?
there is nice how-to on http://boolberry.com/howto.html  Wink
you have to use command line. or you can create .bat file if you are using windows
hero member
Activity: 616
Merit: 500
So,

I wanted to start mining, but simplewallet just pops up for a second and then closes.. what am I doing wrong?
sr. member
Activity: 295
Merit: 250
legendary
Activity: 2142
Merit: 1131
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

900kh/s is still fine for solo. You have temporally bad luck or something is wrong in your setup.

So according to my calculations, im going to be seeing 0,0324 per day... not gonna bother Sad

You're right. Your hash must be too low. Add more computers on the same address or wait for a pool.

(24*60/2)*(your_hashrate)/(64000000000/120)= block per day
Thanks. I just did computed my total coins per day with my hashrate (360,000) and it came out to 0.486 blocks or 8.505 coins per day.


Around 0.5 block per day is fine.
I would keep mining above 0.33 blocks per day.

member
Activity: 140
Merit: 12
I have a good feeling about this coin.
hero member
Activity: 938
Merit: 1001
Have any exchanges approached boolberry devs about carrying this coin? 

Boolberry needs a permanent name before we get on any exchanges. Poloniex is aware of Boolberry.


Boolberry (HoneyPenny) Name Contest

Winning Name gets 125 BBR




sr. member
Activity: 280
Merit: 250
Who cares?
Have any exchanges approached boolberry devs about carrying this coin? 
legendary
Activity: 1106
Merit: 1000
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
sr. member
Activity: 336
Merit: 250
easier:
hashrate*86400/difficulty=blocks per day

how do you find out the diff? the "diff" command doesn't seem to be in the daemon...

type "set_log 1" in daemon and it shows the latest difficulty after each block.
Also, "print_bc 1" shows blocks from 1 to latest.
Jump to: