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

[jl777]

The first bounty is for a .dmg file and the script that produces the .dmg file so that future versions can be made by anybody with Xcode, correct? Who will verify, test?

The second one is for 32 bit Win7 cmake files that work (assuming the code isnt dependent on 64bit mode).

I can hold bounties and create new threads with links in first post. Verify and I will setup and post info.

Yes, need both .dmg file and  a way for anybody with Xcode to make new versions. I will be able to test it, but of course best if more than just I do.

I have already authorized the contractor to start on the .dmg + .dmg making script

For the second one, yes I want to be able to build a 32 bit windows version

James

P.S. This thread is not so active, could you just use this thread to post info? I can barely follow all the threads I need to as it is

[jl777]

I have cryptonote newbie questions:

A) How do you generate the payment ID? I am trying to automate point to point anon payment and it seems I need a payment ID to be generated by the receiver. Also, I am assuming that this payment ID is sensitive, eg. dont want to be broadcasting this for all to see as that could allow others to trace the payment. However, maybe cryptonote works such that it is OK to have the payment ID public? The answer to this determines my approach for auto anon payments

B) fake_outs_count 0 seems to offer no anonimity, but if I set it to a high value and there are no other addresses avaiable, then it seems the tx never goes out? So, if everybody is waiting for big fake_outs_count at first, it deadlocks. I just want to make sure I understand this. Are all addresses seen on the blockchain part of the fake_outs_count pool or is there some other factor that is needed for them to be used?

C) is the dust_policy something that can be changed per transaction, or is it hardcoded? I tried to set DEFAULT_FEE to 0 and DEFAULT_DUST_THRESHOLD to 1, but it still charges 1.0 for txfee and any fractional amount also gone. Not even sure where it goes to... My idea is to make a totally frictionless anon tx possible, so I want to have no txfee and no dusting, but not sure how to achieve this as dust_policy seems to override my settings.

James

A) I guess this is just a random number formatted properly? Still cant figure out if there is info leaked by making the payment ID public, I am assuming so.

B) need help on this one...

C) this seems to have fixed itself, must have not recompiled all the modules when I was getting strange errors

[btc-mike]

Since dga has Xcode for Mac already, i don't hold a new bounty for for that.   

What is the Windows 32 bit bounty for? Daemon, cpuminer-multi, GUI wallet, simplewallet?

jl777 - zoidberg will answer your questions in the morning.

[jl777]

Since dga has Xcode for Mac already, i don't hold a new bounty for for that.   

What is the Windows 32 bit bounty for? Daemon, cpuminer-multi, GUI wallet, simplewallet?

jl777 - zoidberg will answer your questions in the morning.

win32 bounty for Daemon and simplewallet

[btc-mike]

     Everyone who is mining on testserver: please pull sources and recompile miner!

Everyone with Linux, please use our STRATUM test pool located at http://162.243.210.156.

We need to verify the stratum code finds blocks.

Pull the the latest code and compile. Here are the commands I use on Ubuntu 14.04:

Code:

sudo apt-get install libcurl4-openssl-dev libncurses5-dev pkg-config automake yasm git
git clone https://github.com/cryptozoidberg/cpuminer-multi
cd cpuminer-multi
./autogen.sh
./configure CFLAGS="-O3"
make

run minerd with:

Code:

./minerd -a wildkeccak -o stratum+tcp://162.243.210.156:7778 -u <BBR-ADDRESS> -p x -t <THREADS>

I put a lot hash power onto pool but it will take a while to find block at current hashrate. If anyone with a lot of EC2 instances could pool mine for a little while, it would help verify the stratum is ready for full release (PM me - I will pay for test hash).

[Sy]

Any win x64 version of that stratum miner?

I've already pointed my 3 linux rigs onto the pool, not much but "not much" times "many" would still do the trick

[crypto_zoidberg]

    Yesterday i've changed pool ports, to leave old version of miners behind. Please update new to last version.


    Miner:  https://github.com/cryptozoidberg/cpuminer-multi

    

Code:

./minerd -a wildkeccak -o stratum+tcp://162.243.210.156:7778 -u        1L1ZPC9XodC6g5BX8j8m3vcdkXPiZrVF7RcERWE879coQDWiztUbkkVZ86o43P27Udb3qxL4B41gbaGpvj3nS7DgFZauAZE  -p x -P -D -t 4
    

    Pool state: http://162.243.210.156/

[btc-mike]

Good News Everybody!

The stratum miner code has been stress-tested and is ready for release. The test pool was hammered with a lot of hash power and did well. We have found 2 blocks this morning. Here is the pool address to see for yourself -> http://162.243.210.156/

ALL Pool Operators need to update their pools. The pool code and daemon have had updates.

https://github.com/cryptozoidberg/node-boolberry-pool
https://github.com/cryptozoidberg/boolberry

ALL Linux Miners need to recompile. If you did not compile in last 12 hrs, you are behind.

https://github.com/cryptozoidberg/cpuminer-multi

Our test pool is currently the only one with the working code. Extremepool will be updated shortly.

As always, if you have any questions, post here. I am also in IRC if you want help or just want to chat.

Good Luck!

[33zer0w0lf]

Extreme Pool

Since the test pool has found blocks now, and my independent tests confirm the pool and new stratum miner should be working fine.
I am announcing the new boolberry public pool is open @ http://boolberry.extremepool.org

If you care currently mining @ bbr.extremepool.org please move your miners over to http://boolberry.extremepool.org.

Get the latest stratum miner for boolberry!

Enjoy!

[crypto_zoidberg]

P.S. I will pay 100 BBR for 32 bit Win7 cmake files that work (assuming the code isnt dependent on 64bit mode)

Even if we build 32bit version of BBR, i can't grant that this will work fine since there a lot of places that potentially buggy in 32bit.
Another reason is that 4 GB will be not enought for normal work after say ... 2-3 months. As i know monero already had this problems.
That's why i'm not going to support 32bit. But, probably i'll fix this issue after i close all critical tasks.
But, if someone will build 32-bit, please, before announce - run coretests and unittests to ensure that currency core is not broken.

[crypto_zoidberg]

I got things compiling for Mac and Ubuntu, but windows is not working. Is 32 bit Win 7 supported?

No. 64 bit only.

Any chance somebody can make the 32 bit build environment? I am not Windows guy and there are still a lot of 32 bit windows around for some reason.

On the Mac .dmg and script to make .dmg I have some bad news. The contractor to do this says it will cost 155 EUR, so more like 500 BBR. I had bounty commitment of 200 BBR and I can add 100 BBR of my own, but that is still 200 BBR short. Hopefully we can get some other donator to make up the difference?

James

P.S. I will pay 100 BBR for 32 bit Win7 cmake files that work (assuming the code isnt dependent on 64bit mode)

+200 BBR to the bounty as long as it's done in a way that can be carried forward simply and isn't just a one-time hack to get it working.

(btc-mike, are you hosting that bounty?  If so, to what address should I send some BBR?)

Thanks!
I am coordinating this mini-project
The deliverable is for a .dmg file and the script that produces the .dmg file so that future versions can be made by anybody with Xcode

James

Edit: go ahead and send the BBR to btc-mike, I have no need to hold the funds

I have vps host with macos, when script will be available i'll integrate it into project build system to get builded automatically.

[33zer0w0lf]

Extreme Pool

Directions for mining using stratum (Linux only):

1.  Get and install the new minerthe new miner  

Code:

git clone https://github.com/cryptozoidberg/cpuminer-multi     

cd Cpuminer-multi

Code:

./autogen.sh

Code:

./configure CFLAGS="-O3"

Code:

make

2.  Now that the miner is downloaded and installed, using the following command to mine on Extreme Pool.

Code:

./minerd -a wildkeccak -o stratum+tcp://boolberry.extremepool.org:7777 -u <your bbr address> -p x -t <threads>

[crypto_zoidberg]

I have cryptonote newbie questions:

A) How do you generate the payment ID? I am trying to automate point to point anon payment and it seems I need a payment ID to be generated by the receiver. Also, I am assuming that this payment ID is sensitive, eg. dont want to be broadcasting this for all to see as that could allow others to trace the payment. However, maybe cryptonote works such that it is OK to have the payment ID public? The answer to this determines my approach for auto anon payments

B) fake_outs_count 0 seems to offer no anonimity, but if I set it to a high value and there are no other addresses avaiable, then it seems the tx never goes out? So, if everybody is waiting for big fake_outs_count at first, it deadlocks. I just want to make sure I understand this. Are all addresses seen on the blockchain part of the fake_outs_count pool or is there some other factor that is needed for them to be used?

C) is the dust_policy something that can be changed per transaction, or is it hardcoded? I tried to set DEFAULT_FEE to 0 and DEFAULT_DUST_THRESHOLD to 1, but it still charges 1.0 for txfee and any fractional amount also gone. Not even sure where it goes to... My idea is to make a totally frictionless anon tx possible, so I want to have no txfee and no dusting, but not sure how to achieve this as dust_policy seems to override my settings.

James

1. Payment ID is generated by payments receiver and included into transaction as a prove that sender is really created this transaction. This is not the best solution, as i know this was made as workaround. I have ideas how to go without payment_id but sender need to communicate with receiver directly.

2. I don't know what you mean here, cryptonote blockchain don't have user addresses in it. fake_outs_counter select amounts to be mixedin into ringsignature (output keys is used for this).

3. Fee can't be 0(network rule). Also, pools will not gonna mine transactions with low fee, and according to last commits will not even relay it. DEFAULT_DUST_THRESHOLD also can't be changed  since it used in blockreward formula. Don't know how you gonna avoid "dusting"... i've removed dust from block reward, but dust will appear from exchanges or bbrdice, or any other payment services.

[dga]

I have cryptonote newbie questions:

A) How do you generate the payment ID? I am trying to automate point to point anon payment and it seems I need a payment ID to be generated by the receiver. Also, I am assuming that this payment ID is sensitive, eg. dont want to be broadcasting this for all to see as that could allow others to trace the payment. However, maybe cryptonote works such that it is OK to have the payment ID public? The answer to this determines my approach for auto anon payments

B) fake_outs_count 0 seems to offer no anonimity, but if I set it to a high value and there are no other addresses avaiable, then it seems the tx never goes out? So, if everybody is waiting for big fake_outs_count at first, it deadlocks. I just want to make sure I understand this. Are all addresses seen on the blockchain part of the fake_outs_count pool or is there some other factor that is needed for them to be used?

C) is the dust_policy something that can be changed per transaction, or is it hardcoded? I tried to set DEFAULT_FEE to 0 and DEFAULT_DUST_THRESHOLD to 1, but it still charges 1.0 for txfee and any fractional amount also gone. Not even sure where it goes to... My idea is to make a totally frictionless anon tx possible, so I want to have no txfee and no dusting, but not sure how to achieve this as dust_policy seems to override my settings.

James

1. Payment ID is generated by payments receiver and included into transaction as a prove that sender is really created this transaction. This is not the best solution, as i know this was made as workaround. I have ideas how to go without payment_id but sender need to communicate with receiver directly.
r payment services.

I read jl777's question differently:

Is the payment ID in cleartext, or is it encrypted so that only the intended recipient can decode it?

And if it's encrypted, I assume it's done in such a way that it does not enable linking of multiple transactions using the same payment ID?

[teknohog]

2.  Now that the miner is downloaded and installed, using the following command to mine on Extreme Pool.

Code:

./minerd -a wildkeccak -o stratum+tcp://boolberry.extremepool.org:7777 -u <your bbr address> -p x -t <threads>

It seems to pick up the number of CPUs by itself, so you don't really need the -t option.

(I generally use -t `nproc` for all the various cpuminers, because some of them either don't pick it up, or assume things about hyperthreading and AES-NI that don't apply to everyone. Of course try different numbers, but usually the default is the best.)

[crypto_zoidberg]

I have cryptonote newbie questions:

A) How do you generate the payment ID? I am trying to automate point to point anon payment and it seems I need a payment ID to be generated by the receiver. Also, I am assuming that this payment ID is sensitive, eg. dont want to be broadcasting this for all to see as that could allow others to trace the payment. However, maybe cryptonote works such that it is OK to have the payment ID public? The answer to this determines my approach for auto anon payments

B) fake_outs_count 0 seems to offer no anonimity, but if I set it to a high value and there are no other addresses avaiable, then it seems the tx never goes out? So, if everybody is waiting for big fake_outs_count at first, it deadlocks. I just want to make sure I understand this. Are all addresses seen on the blockchain part of the fake_outs_count pool or is there some other factor that is needed for them to be used?

C) is the dust_policy something that can be changed per transaction, or is it hardcoded? I tried to set DEFAULT_FEE to 0 and DEFAULT_DUST_THRESHOLD to 1, but it still charges 1.0 for txfee and any fractional amount also gone. Not even sure where it goes to... My idea is to make a totally frictionless anon tx possible, so I want to have no txfee and no dusting, but not sure how to achieve this as dust_policy seems to override my settings.

James

1. Payment ID is generated by payments receiver and included into transaction as a prove that sender is really created this transaction. This is not the best solution, as i know this was made as workaround. I have ideas how to go without payment_id but sender need to communicate with receiver directly.
r payment services.

I read jl777's question differently:

Is the payment ID in cleartext, or is it encrypted so that only the intended recipient can decode it?

And if it's encrypted, I assume it's done in such a way that it does not enable linking of multiple transactions using the same payment ID?

Oh, sorry.
Payment id is just an array of 32 bytes binary data, randomly generated by receiver(i believe it randomly generated). It is encoded as hexstring to be shown(in exchage web interface) and than it decoded back into 32 bytes of binary data to be placed into transaction extra.
In other words it's just an ID info placed into transaction

[kingscrown]

mining at http://bbr.extremepool.org/ but when trying to 'search' it get freezed and never finds me

[33zer0w0lf]

mining at http://bbr.extremepool.org/ but when trying to 'search' it get freezed and never finds me

bbr.extremepool.org is no more.

New pool with new code is http://boolberry.extremepool.org

[kingscrown]

mining at http://bbr.extremepool.org/ but when trying to 'search' it get freezed and never finds me

bbr.extremepool.org is no more.

New pool with new code is http://boolberry.extremepool.org

oh ok. still have issues with 'search'.
can u check?

[jl777]

I have cryptonote newbie questions:

A) How do you generate the payment ID? I am trying to automate point to point anon payment and it seems I need a payment ID to be generated by the receiver. Also, I am assuming that this payment ID is sensitive, eg. dont want to be broadcasting this for all to see as that could allow others to trace the payment. However, maybe cryptonote works such that it is OK to have the payment ID public? The answer to this determines my approach for auto anon payments

B) fake_outs_count 0 seems to offer no anonimity, but if I set it to a high value and there are no other addresses avaiable, then it seems the tx never goes out? So, if everybody is waiting for big fake_outs_count at first, it deadlocks. I just want to make sure I understand this. Are all addresses seen on the blockchain part of the fake_outs_count pool or is there some other factor that is needed for them to be used?

C) is the dust_policy something that can be changed per transaction, or is it hardcoded? I tried to set DEFAULT_FEE to 0 and DEFAULT_DUST_THRESHOLD to 1, but it still charges 1.0 for txfee and any fractional amount also gone. Not even sure where it goes to... My idea is to make a totally frictionless anon tx possible, so I want to have no txfee and no dusting, but not sure how to achieve this as dust_policy seems to override my settings.

James

1. Payment ID is generated by payments receiver and included into transaction as a prove that sender is really created this transaction. This is not the best solution, as i know this was made as workaround. I have ideas how to go without payment_id but sender need to communicate with receiver directly.

2. I don't know what you mean here, cryptonote blockchain don't have user addresses in it. fake_outs_counter select amounts to be mixedin into ringsignature (output keys is used for this).

3. Fee can't be 0(network rule). Also, pools will not gonna mine transactions with low fee, and according to last commits will not even relay it. DEFAULT_DUST_THRESHOLD also can't be changed  since it used in blockreward formula. Don't know how you gonna avoid "dusting"... i've removed dust from block reward, but dust will appear from exchanges or bbrdice, or any other payment services.

1. My concern is that in order for Alice to Pay Bob using payment ID, if that ID (random or not) is public information and the ID ends up in the blockchain, couldnt an attacker start creating a correlation predictor based on payments to the public ID? Also it is possible to send payments without any payment ID at least it worked in my tests.

2. Sorry, I am still learning cryptonote so I just assumed the dest address is there, I guess it is the payment ID address that is there and unless that was communicated privately, info is leaked

3. After fiddling with things all weekend (half a dozen places that assumed non-zero fees!), I did manage to get it working. My use case wont have any mining, just very low difficulty (big sleep in miner loop) so that we get blocks every minute.

After problems in every step of the process I finally got it to accept a no-fee tx and then finally release it tx from the mempool and once that worked, all seemed pretty happy. I've already premined 99.2% and when I get to 99.999% the block reward will be small enough to discourage any cheating. The purpose of pNXT is to map 1:1 to NXT so that people can send NXT from its web GUI and have it use boolberry cryptonote pNXT for the transfer.

James

P.S. Good point about 32 bit mode, it seems we need to use a memory mapped blockchain file for it to have a chance.

P.P.S. zerofees should encourage a lot of tx, which provides best privacy, at least from a practical point. I guess I need to think about regular purges. With pNXT it is a matter of forcing everyone to redeem it and reset the blockchain, but that does sound rather messy...