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

[smooth]

oaes_key_gen() does not seem to be used anywhere, and the function is not documented, but why it uses rand() to generate the key? 

Dumb, but there is good code to generate keys using an entropy source somewhere else. (I forgot where but I did review it.)

Someone should comment out oaes_key_gen and recompile to make sure it really isn't being used.

[otila]

oaes_key_gen() does not seem to be used anywhere, and the function is not documented, but why it uses rand() to generate the key? 

Dumb, but there is good code to generate keys using an entropy source somewhere else. (I forgot where but I did review it.)

Someone should comment out oaes_key_gen and recompile to make sure it really isn't being used.

Did that, programs linked OK.

[digicoin]

The public key in CryptoNote is way too long. Should we make it shorter or it is on purpose?

It reminds me of Bitcoin address. It is a hashed version of the public key. The public key is 256 bits long, and the final hash (ie. address) is 160 bits long.

I am little bit curious about CryptoNote's technical background of an address

PS: Sorry, I haven't read the code yet

[tacotime]

The public key in CryptoNote is way too long. Should we make it shorter or it is on purpose?

It reminds me of Bitcoin address. It is a hashed version of the public key. The public key is 256 bits long, and the final hash (ie. address) is 160 bits long.

I am little bit curious about CryptoNote's technical background of an address

PS: Sorry, I haven't read the code yet

The address are similar in size to those of Bitcoin stealth addresses.  There is no conceivable way to shorten them that would lot lead to attacks through ECDH.  I would suggest you read up on stealth addressing.

[crypto_zoidberg]

Good news!
We've done implementing alerts signed by developers. Special kind of signed data propagated via COMMAND_HANDSHAKE and COMMAND_TIMED_SYNC.
Just tested it and commited changes to master branch. (it seems to work ok, but possible bugs, write me if you find some)

Now we've finished with all things that we announced (and even little more).

Before start we need:
1. get new suitable name (https://bitcointalk.org/index.php?topic=588905.0)
2. approve monetization schema (https://bitcointalk.org/index.php?topic=590520.0)
3. decide about hash details (https://bitcointalk.org/index.php?topic=588421.0)

Will answer to posts soon.

[digicoin]

I think that we need to mailboxd to read and store such alert history. Is such alerts stored in blockchain?

[crypto_zoidberg]

I think that we need to mailboxd to read and store such alert history. Is such alerts stored in blockchain?

No.
There are few abstraction layers in CryptoNote code(as described on our page http://honeypenny.org/design.html), Blockchain lies on upper level.
We've done this feature on p2p level in two reasons:
1. P2p code could be taken for another project based on p2p technology, so this feature would be useful.
2. Having alerts based on blockchain makes more complicated to push alert devs have to look for some of miners and ask them to do it.

Anyway, collecting this alerts archive may be done with local daemon storage.

[digicoin]

Is it possible to use this feature to send a p2p message from user A to user B where the message is encrypted, unfakable?

[crypto_zoidberg]

Is it possible to use this feature to send a p2p message from user A to user B where the message is encrypted, unfakable?

Unfortunately no.

[crypto_zoidberg]

Good news!
We've added UPnP support with reannouncing every 20 minutes (like bitcoin do). Just merged it in master branch.
Anyone who have UPnP router - please check this - or by running daemon, or just run functional_tests --test_miniupnp.
We've checked it on two devices - one was correctly configured, other failed.

[emontmon]

can you change the op regarding network launch

1. will be launched with prior notice of two days.
2. will launch network with 2 days prior notice. estimated date

I keep thinking I missed it as it says this week as of last week. So i guess I am not sure that you launched already

[otila]

What's the purpose of mul_f::keccakf_m function, keccak modified to use multiplying in bc[5] setup?

[superresistant]

The name is quite ridiculous IMO.

It's funny though.

[otila]

Code:

[ 42%] Building CXX object src/CMakeFiles/crypto.dir/crypto/keccak_modified.cpp.o
In file included from /c/honeypenny/src/crypto/keccak_modified.cpp:6:0:
/c/honeypenny/src/crypto/keccak_modified.h: In function ‘pod_operand_a crypto::xor_pod(const pod_operand_a&, const pod_operand_b&)’:
/c/honeypenny/src/crypto/keccak_modified.h:30:5: error: ‘hash’ is not a member of ‘crypto’
     crypto::hash r;
     ^

[btc-mike]

The name is quite ridiculous IMO.

It's funny though.

There is another thread for name change suggestions

Project name contest: https://bitcointalk.org/index.php?topic=588905.0

[otila]

tried with empty ~/.HoneyPenny

Code:

2014-May-07 19:11:12.235978 [P2P7]ERROR /c/honeypenny/src/currency_core/blockchain_storage.cpp:1139 Client sent wrong NOTIFY_REQUEST_CHAIN: genesis block missmatch: 
id: <830ec1d9917286cd95ac0128022900dc452c33d9d29974ae304bff430fc10353>, 
expected: <6d0a2fd27d7ba5867d966528d7ac0334df54ef38b1826eab9e651431e7d7a847>,
 dropping connection
2014-May-07 19:11:12.236062 [P2P7]ERROR /c/honeypenny/src/currency_protocol/currency_protocol_handler.inl:365 [107.170.228.11:10101 OUT]Failed to handle NOTIFY_REQUEST_CHAIN.

[TheMightyX]

Can we get an update on the announcement of launch?

The OP says April 27 and launch will be "this week", which it obviously wasn't.

Please be more clear.
Thanks

[crypto_zoidberg]

What's the purpose of mul_f::keccakf_m function, keccak modified to use multiplying in bc[5] setup?

Little surprise for ASIC engineers, considered that effective 64-bit multiplication is pretty expensive to have on each core. (unlike normal CPU)
Just to reduce the enthusiasm.

[crypto_zoidberg]

When its launching? Will you chose the new name right away?

11-12 May

[emontmon]

Can this be mined with the galaxy s5