[Passed] Motion to provide seed funding for B&C Exchange - a decentralized exchange built on the Peershares platform

Has anyone compiled a r-pi 2 version of the gui less bcexchanged yet? It’s stake time :smile:

Nope. Had trouble trying it, but so far no help fixing the issues.

In my spare time (of which there isn’t much at the moment) I’ve been experimenting with using Docker to create an ARM build environment that can be run on a normal (x64) computer.
I have this so far https://github.com/inuitwallet/Docker-ARM-NuBits-client-build
It starts the build process but normally fails a part way through so needs a bit more work. It’s just for the NuBits client currently but could easily be ported to B&C once it’s working.
If anyone knows Docker and wants to take a look, feel free. I think it’s just missing a dependency but I’m not sure which. I’ll run it again in a bit and get the actual error message the make fails with

2 Likes

Sorted by views, the [ANN] thread at the bitcointalk.org “Project Development” board is in the top 25 (current place: 23) of all ever announced/discussed projects (more than 7,000 in this board):

http://imgur.com/MQ6AJGK

Total number of views: 50,050
Total number of posts: 487
(bitcointalk.org time: July 29, 2015, 12:16:46 PM)

That’s impressive!

4 Likes

For those who want to generate their own set of B&C keys, I base58 decoded a set in advance:

private key prefix: 0x99
public key prefix: 0x12

After initial problems to build a bcexchanged on my RaPi2 I tried again.
Here’s a dcoumentation of my steps:

sudo apt-get update
sudo apt-get install libcurl4-openssl-dev #libcurl is required to build from the source, although not stated in doc/build.txt; make sure to have all other dependencies installed
mkdir ~/bce
cd ~/bce
wget https://bitbucket.org/JordanLeePeershares/bcexchange/get/e472f471107c.zip
unzip e472f471107c.zip
cd ~/bce/JordanLeePeershares-bcexchange-e472f471107c/src
sed -i 's/USE_UPNP:=0/USE_UPNP:=-/' makefile.unix #disables UPNP; I don't have the dependencies installed and don't need UPNP
make -f makefile.unix

Et voila, bcexchanged ready after some time (thanks to the RaPi2 being fast as hell compared to the RaPi1 :wink: )

Tried starting it and it worked :slight_smile:

bcexchanged --daemon
B&C Exchange server starting
Error: To use the "-daemon" option, you must set a rpcpassword in the configuration file:
 /home/pi/.bcexchange/bcexchange.conf
It is recommended you use the following random password:
rpcuser=nurpc
rpcpassword=bVCSDYtSZyo9SNIw31O10bRa47Y9c8qO8mJT4N0cJSQf

Still some Nu left - but hooray, it’s working :wink:

3 Likes

??

That’s the output which is generated if you start bcexchanged with the “–daemon” flag

Can someone remind me of the current minting stats?

Minimum coinage?
Minting reward?

I think I’m right in saying that the minimum coinage is 1 BKS (1BKS == 10000 NSR)
The minting reward is 0.1 BKS
edit: Ah coin-age not coinage. ignore that first bit then (I think it remains as 7 days)
damn decimal point too! yup, 0.01 not 0.1

2 Likes

According to the design document (Section “Use case: Minter and shareholder”, page 19) the minimum coinage for minting is said to be 7 days.
The minting reward is reported to be 0.01 BKS and the minimum mount of BKS to mint is 1.

0.01 is right, but you only need 1 BKS to mint. The threshold is lower (by 4x) but the reward is greater (by 2.5x) than for nsr.

Oh, thank you for pointing that out. I misread your post at bitcointalk.org (which clearly states that 1 BKS is required to mint) and have corrected my last post.

Thanks for all the answers so far.

Which port is B&C using?

I see
tcp 0 0 0.0.0.0:2239 0.0.0.0:* LISTEN 2888/bcexchanged
tcp 0 0 127.0.0.1:2240 0.0.0.0:* LISTEN 2888/bcexchanged
tcp 0 0 127.0.0.1:2241 0.0.0.0:* LISTEN 2888/bcexchanged

on netstat

Willy

tcp/2239 is what all connected peers show

bcexchanged getpeerinfo
[
    {
        "addr" : "62.210.15.44:2239",
        "services" : "00000001",
        "lastsend" : 1438376669,
        "lastrecv" : 1438376668,
        "conntime" : 1438334577,
        "version" : 2000000,
        "subver" : "/Siglee:3.0.0/B&C Exchange:3.0.0(v3.0.0-unk-beta)/",
        "inbound" : false,
        "releasetime" : 0,
        "height" : 34349,
        "banscore" : 0
    },
    {
        "addr" : "176.9.113.75:2239",
        "services" : "00000001",
        "lastsend" : 1438376669,
        "lastrecv" : 1438376669,
        "conntime" : 1438334578,
        "version" : 2000000,
        "subver" : "/Siglee:3.0.0/B&C Exchange:3.0.0(v3.0.0-RC2-beta)/",
        "inbound" : false,
        "releasetime" : 0,
        "height" : 34349,
        "banscore" : 0
    },
    {
        "addr" : "104.130.130.34:2239",
        "services" : "00000001",
        "lastsend" : 1438376497,
        "lastrecv" : 1438376668,
        "conntime" : 1438334578,
        "version" : 2000000,
        "subver" : "/Siglee:3.0.0/B&C Exchange:3.0.0(v3.0.0-RC1-beta)/",
        "inbound" : false,
        "releasetime" : 0,
        "height" : 34349,
        "banscore" : 0
    },
    {
        "addr" : "62.4.15.180:2239",
        "services" : "00000001",
        "lastsend" : 1438376657,
        "lastrecv" : 1438376668,
        "conntime" : 1438334579,
        "version" : 2000000,
        "subver" : "/Siglee:3.0.0/B&C Exchange:3.0.0(v3.0.0-unk-beta)/",
        "inbound" : false,
        "releasetime" : 0,
        "height" : 34349,
        "banscore" : 0
    },
    {
        "addr" : "67.170.53.99:2239",
        "services" : "00000001",
        "lastsend" : 1438376669,
        "lastrecv" : 1438376669,
        "conntime" : 1438334596,
        "version" : 2000000,
        "subver" : "/Siglee:3.0.0/B&C Exchange:3.0.0(v3.0.0-RC2-beta)/",
        "inbound" : false,
        "releasetime" : 0,
        "height" : 34351,
        "banscore" : 0
    },
    {
        "addr" : "120.24.210.125:2239",
        "services" : "00000001",
        "lastsend" : 1438376669,
        "lastrecv" : 1438376669,
        "conntime" : 1438334672,
        "version" : 2000000,
        "subver" : "/Siglee:3.0.0/B&C Exchange:3.0.0(v3.0.0-RC1-beta)/",
        "inbound" : false,
        "releasetime" : 0,
        "height" : 34351,
        "banscore" : 0
    },
    {
        "addr" : "73.171.28.236:2239",
        "services" : "00000001",
        "lastsend" : 1438376668,
        "lastrecv" : 1438376668,
        "conntime" : 1438335316,
        "version" : 2000000,
        "subver" : "/Siglee:3.0.0/B&C Exchange:3.0.0(v3.0.0-RC1-beta)/",
        "inbound" : false,
        "releasetime" : 0,
        "height" : 34362,
        "banscore" : 0
    },
    {
        "addr" : "114.215.118.148:2239",
        "services" : "00000001",
        "lastsend" : 1438376669,
        "lastrecv" : 1438376669,
        "conntime" : 1438335922,
        "version" : 2000000,
        "subver" : "/Siglee:3.0.0/B&C Exchange:3.0.0(v3.0.0-RC1-beta)/",
        "inbound" : false,
        "releasetime" : 0,
        "height" : 34373,
        "banscore" : 0
    }
]

You should be able to specify a port (if it shall be different from 2239) in the bcexchange.conf

port=xyz
1 Like

Oh boy… that sure was the easiest solution. I can stop skimming the source code now :smiley:
Thank you so much.

2 Likes

I can’t read code. I need to use other tools :wink:

After successful compilation of bcexchanged on my RaspberryPi2 (and running it stable since then (July 31, 2015)) I’ve experienced different behaviour of “bcexchanged” and “nud”.

Shortly after the daemon is started, bcexchanged is responsive to RPC, e.g.

bcexchanged getinfo

while nud is complaining about “error: couldn’t connect to server” for several minutes. Is this due to the bigger blockchain of Nu? Is there a kind of integrity scan running? Both Nu and BCE wallets are empty. So there’s no need to search for transactions related to keys.
Oh wait - the client needs to scan the blockchain anyway, because it wouldn’t know that there are no transactions to private addresses in the wallet, right? Even an “empty” wallet contains keys…
…but even if that scan is going - why does it interfere with executing RPC commands?

The RAM assignment is very different as well.

  • bcexchanged uses ~6% RAM (60 MB)
  • nud uses ~45% RAM (450 MB)

Is that difference of RAM assignment due to changes in the Nu 2.0 code from which BCE was forked?
Would compiling nud from 2.0 code reduce nud RAM assignment?

The B&C Exchange OS X application was announced a few days ago.

2 Likes

It used to be at 8 connections, but as of late it has dropped to only 1. Still staking so no complaints, but wondering if anybody else has the same issue?