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

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!

    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

    

    Pool state: http://162.243.210.156/

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

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:


run minerd with:

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).

win32 bounty for Daemon and simplewallet

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.

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

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

I have Xcode and will verify/test the script for MacOS dmg build.

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.

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

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

+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?)

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)

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

No. 64 bit only.

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

No docs, just my ramblings

From a NXT point of view, people will want to send NXT and have it be anonymous. If it was just a gateway conversion of NXT -> BBR -> ring signature send -> dest BBR -> dest NXT, then the problem is the converting of NXT to BBR and back without getting hit by big spreads and lack of liquidity.

In NXT there are assets, basically colored coins. I made a privateNXT asset that is mapped 1:1 to NXT. I also made a BBR fork I am calling pNXT and the idea is to bind the pNXT to the privateNXT asset.
So, privateNXT -> pNXT -> ring sig send -> dest pNXT -> dest privateNXT can happen without any open market exchange issues.

Once I get this working, I hope to be able to use the same code base to simultaneously process BBT blockchain, but at worst it is a matter of having two processes as pNXT wont have any mining and CPU usage is < 3%

James

I've merged my NXTservices into the BBR source base and it has libwebsockets to create API interface via 127.0.0.1:7777
Since we already have a web GUI that uses this interface, once I create a payments API, it will be a matter for the GUI guys to make it easy to use.
My stuff is all in C, but I got hooks in to the main C++ classes and have gotten easy stuff like current height, account balance, so next step is tackling actually sending a payment.

If you have any ideas on a simple but not too simple payment API that would help, I am cryptonote newbie

James

interesting.  how does this work?  any doc you can point me to?

"NXT internal privateNXT asset and pNXT BBR fork that map 1:1 to avoid having to exchange NXT <-> BBR in thin markets"