[BBR] Boolberry: Privacy and Security - Guaranteed Since 2014

[ripplebtc]

WTB 2000 BBR @ 0.001 BTC (you send first or escrow)

[crypto_zoidberg]

IMPORTANT NOTICE

Aliases now have restricted to this alowed characters:

Code:

#define VALID_ALIAS_CHARS     "0123456789abcdefghijklmnopqrstuvwxyz-."

I'm very sorry to all who already assigned some extra symbols.
This is made to protect your aliases from "pfishing" or confusing cheats.
For example if there some well-known @goodpool alias, i want to make this name safe from same-looking names like @Goodpool or @goodpóól, or @goodpoo|.

I'll be back when i finish current developent iteration, with short description of what is done.

Good "luck".
Your Zoidberg.

[surfer43]

Good roadmap. GUI and database are very needed features. Hopefully the "Nice GUI" is much nicer than Bitcoin-qt! 

[hornyPo]

I get a error on Ubuntu 13.10 in the daemon

Code:

2014-Mai-21 23:28:16.33016 [P2P6][sock 94] Some problems at write: Broken pipe:32

and then a lot of red output.

Code:

2014-Mai-21 23:28:58.465427 [P2P3] ERROR /home/user/boolberry/contrib/epee/include/... 

...

in the Monero thread someone have the same problem.

e.g.:
https://bitcointalk.org/index.php?topic=583449.msg6559881;topicseen#msg6559881

[otila]

Code:

2014-Mai-21 23:28:16.33016 [P2P6][sock 94] Some problems at write: Broken pipe:32

That should be moved to log level 2 .. don't worry about it.

[crypto_zoidberg]

I see transaction with about 450BBR that stuck in memory pools(and two other transactons also).

The problem is in fee.
Wallet use just default hardcoded fee(and here is problem actually).
At the other hand daemon's transaction pool use "greedy" policy to collect transactions into block - and this transaction not fits to this conditions (it depends of  fee/tx_size ratio).

To solve this problem we need to improve wallet to set fee up to current tx_pool state, to have fee/tx_size ratio enough to be included in block.
It will be implemented soon, but for current version - i strongly recomend you to send big amount with few small transfers not bigger than 100BBR


Senders of those transactions can PM me, i'll try to help with this issue.

[crypto_zoidberg]

Code:

2014-Mai-21 23:28:16.33016 [P2P6][sock 94] Some problems at write: Broken pipe:32

That should be moved to log level 2 .. don't worry about it.

good point!

I've just fixed one bug that made this messages apeared frequently.

[crypto_zoidberg]

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

Code:

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!

[creamynebula]

Is the new version already released?, including binaries?

[btc-mike]

Is the new version already released?, including binaries?

I just downloaded windows and checked dates. It has today's date.

[creamynebula]

great, thank you

[molecularfir]

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)
http://boolberry.com/files/conn_fail.jpg
Now it's fine.
And also it could be seen as this problem:

I get a error on Ubuntu 13.10 in the daemon

Code:

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!

I just updated from source and lost roughly a 1/3 of my hashing power. What's going on cryto?

Some strange error messages appearing in the logs too:

2014-May-21 23:23:47.160280 [P2P5]ERROR /home/ubuntu/boolberry/contrib/epee/include/net/abstract_tcp_server2.inl:732[bool epee::net_utils::boosted_tcp_server<t_protocol_handler>::connect(const string&, const string&, uint32_t, epee::net_utils::boosted_tcp_server<t_protocol_handler>::t_connection_context&, const string&) [with t_protocol_handler = epee::levin::async_protocol_handler<nodetool::p2p_connection_context_t<currency::currency_connection_context> >; std::string = std::basic_string<char>; uint32_t = unsigned int; epee::net_utils::boosted_tcp_server<t_protocol_handler>::t_connection_context = nodetool::p2p_connection_context_t<currency::currency_connection_context>]][sock -1] Failed to start connection, connections_count = 8
2014-May-21 23:23:47.160395 [P2P5]Connect failed to 107.170.127.203:10101
2014-May-21 23:23:47.160494 [P2P5]Connecting to 107.170.142.183:10101(white=0, last_seen: d0.h0.m0.s1)...
2014-May-21 23:23:47.435512 [P2P4][107.170.142.183:10101 OUT] COMMAND_HANDSHAKE INVOKED OK
2014-May-21 23:24:27.916911 [P2P4]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= <412a5f12c489a12af5fe1c4006ed15bec0e7e766b5f9a091a71d42ee01972072> used already spent key images
2014-May-21 23:24:27.917065 [P2P4]Transaction verification failed: <412a5f12c489a12af5fe1c4006ed15bec0e7e766b5f9a091a71d42ee01972072>
2014-May-21 23:24:27.917166 [P2P4][107.170.229.35:10101 OUT]Tx verification failed, dropping connection
2014-May-21 23:24:28.051078 [P2P5]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= <412a5f12c489a12af5fe1c4006ed15bec0e7e766b5f9a091a71d42ee01972072> used already spent key images
2014-May-21 23:24:28.051220 [P2P5]Transaction verification failed: <412a5f12c489a12af5fe1c4006ed15bec0e7e766b5f9a091a71d42ee01972072>

[btc-mike]

Some fresh news, to keep all informed

...

All the bests!

I just updated from source and lost roughly a 1/3 of my hashing power. What's going on cryto?

...

Please provide more info to help crypto_zoidberg with troubleshooting

1. What OS?
2. 32 or 64 bit?
3. What CPU?
4. How much RAM?
5. What was your hashrate before?
6. What is your hashrate now?

[molecularfir]

Some fresh news, to keep all informed

...

All the bests!

I just updated from source and lost roughly a 1/3 of my hashing power. What's going on cryto?

...

Please provide more info to help crypto_zoidberg with troubleshooting

1. What OS? Ubuntu Saucy Salamander (development branch) (GNU/Linux 3.11.0-8-generic x86_64)
2. 32 or 64 bit? 64
3. What CPU? High Frequency Intel Xeon E5-2670 v2 (Ivy Bridge) Processors
4. How much RAM? 60Gb
5. What was your hashrate before? ~1500000
6. What is your hashrate now? 1101384

[molecularfir]

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>

[ripplebtc]

WTB 2000 BBR @ 0.001 BTC (you send first or escrow)

[surfer43]

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?

[33zer0w0lf]

Sorry about this man, i'll help with pool protocol and thin miner to anyone who would have serious intentions to make pool.

I want to make a pool but the algo seems too complex for the pool to check the hash.

Hash check is much easier than on bytecoin/monero. You just need to use another protocol with incremental delivering scratchpad to client.

I have a cryptonote pool already setup, if there is interest I can setup this Coin on the pool.
PM me.

http://www.extremepool.org

[zeetak]

Sorry about this man, i'll help with pool protocol and thin miner to anyone who would have serious intentions to make pool.

I want to make a pool but the algo seems too complex for the pool to check the hash.

Hash check is much easier than on bytecoin/monero. You just need to use another protocol with incremental delivering scratchpad to client.

I have a cryptonote pool already setup, if there is interest I can setup this Coin on the pool.
PM me.

http://www.extremepool.org

A pool would be great, I'm not finding much solo...

[btc-mike]

WTB 2000 BBR @ 0.001 BTC (you send first or escrow)

If you want to buy/sell, include the link to the buy/sell thread.

https://bitcointalk.org/index.php?topic=616391.0