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

Yurizhai 2015-07-11 18:30:12 UTC #477

Could we get more details on NuShare BKS importing? I’m selecting import, putting in the password and nothing happens.

Nagalim 2015-07-11 19:16:55 UTC #478

Same thing here. It says check the debug window, but the debug window doesn’t say anything special.

sigmike 2015-07-11 19:30:37 UTC #479

If the debug window doesn’t say anything it probably means the wallet was successfully imported. You should have somes addresses in the “Receive” tab with the label “Converted NuShares”. If you don’t and the imported wallet is not empty then it’s a bug. You may have more information in debug.log.

Nagalim 2015-07-11 19:36:42 UTC #480

The debug file is quite long (over 500 pages) and getting longer by the second. I assume my wallet is in the process of importing? Maybe there should be a message somewhere that tells the user that?

cryptog 2015-07-11 22:12:27 UTC #481

Successfully imported my bks as a first test under the following conditions:.

corresponding to 40 nsr
no password set yet in my bsexchange client for either block or credit.
nu client running. (don t know if it is mandatory)

Nagalim 2015-07-12 02:46:30 UTC #483

Alright! I got it working, it was the encryption. Used walletpassphrase in the B&C exchange debug window.

I think it mints in 1 bks outputs.

I’m voting for 0.001 fee for BKS and 0.01 fee for BKC.

Yurizhai 2015-07-12 03:23:29 UTC #484

My B&C client is not encrypted.

It says this in my debug:

importnusharewallet [walletpassword] [rescan=true]
Import NuShares "walletname"
Password is only required if wallet is encrypted
(code -1)

Edit: I’ve since tried encrypting it, unlocking both clients with walletpassphrase command, and it’s still not doing anything other than the message I put above.

sigmike 2015-07-12 06:36:00 UTC #486

It looks like the import feature doesn’t support paths that contain spaces. We will fix that. In the meantime you can copy the wallet to import into a path that doesn’t contain any space an import it from there.

Yurizhai 2015-07-12 06:41:38 UTC #487

Are you talking about the location of the NSR wallet file?

sigmike 2015-07-12 06:42:05 UTC #488

Yes

Yurizhai 2015-07-12 06:53:01 UTC #489

I copied the wallet into a few different folders, paths without spaces as far as I can tell. It doesn’t seem to be working.

sigmike 2015-07-12 06:56:29 UTC #490

Do you get the same “error” in the console? Do you have any address labeled “Converted NuShares” in the “Receive” tab?

Yurizhai 2015-07-12 06:57:50 UTC #491

No addresses named Converted NuShares. I still get the same error. Should I move the original wallet to a different location?

sigmike 2015-07-12 07:02:11 UTC #492

No, the path of the BKS wallet should not matter.

If the NSR wallet is encrypted and the password contains spaces or special characters it may cause the same problem. In that case surround your password with double quotes (").

Sebsebzen 2015-07-12 07:03:50 UTC #493

You may want to try the following:

1). Uninstall BCExchange
2). Delete any leftover files under your User’s AppData\Roaming\BCExchange (be careful!)
3). Copy NuShares wallet (.dat) to something like C:
4). Resintall BCExchange (afterwards don’t encrypt wallet)
5). Import NuShares wallet from C:\

This worked for me!

EDIT: Changed wording about deleting files.

Yurizhai 2015-07-12 07:21:02 UTC #494

@sigmike @Sebsebzen

Well I did both of your suggestions, " " surrounding my password and a fresh install. It worked! Thank you both!

dysconnect 2015-07-12 09:42:01 UTC #495

Does anyone think it would be good for BKC to be tied together more closely to Nu by some sort of single/dual direction proof of burn? For example allowing one to redeem BKC more quickly and conveniently by burning NBT, rather than purchasing on the exchange. The most uncertain part of that is whether B&C shareholders will uphold it in the long term.

matthewd 2015-07-12 11:22:31 UTC #496

I am having problems with the client.

I downloaded and extracted three files:

bcexchange (24,463 kb)
BCExchange-3.0.0-win-setup (9,588 kb)
bcexchanged

I double-clicked on the second option and followed the setup wizard. The process concluded and the client attempted to start. However, I then received the following message:

Assertion failed!
Program: C:\ Program files (x86)\BCexchange\bcexchange.exe
File: src/kernel.cpp, Line 475

Expression: pindex->pprev pindex -> GetBlockHasg() ==
hashGenesisBlock
*

Can you help? I am using the following computer:
Windows 8.1
Intel Core i5-4590T CPU @ 2GHz
64-bit

Thank you in advance

PinkyAndTheBrain 2015-07-12 13:53:58 UTC #497

So I downloaded the client. Private key prefix of bks is set to be 0x99

Not that I’m complaining but I notice that dividend address is a Peercoin address? Wasn’t BTC suppose to be the dividend coin of choice to appeal a broader market?

Nagalim 2015-07-12 14:38:30 UTC #498

This can be done with seeded auctions assuming both NSR and BKS blockchains pass a seeding motion. If Nu pledges to seed with 1000 NBT and burn any received BKC and B&C pledges to seed with 1000 BKC and burn any received NBT, a BKC seller could obtain NBT fairly easily or vice versa.

We could also consider alternative methods for burn gateways. As the price discovery is alleviated (1 NBT = 1 BKC) we can even just use simple burn motions, i.e. submit a motion to B&C to print me BKC if I burn NBT.

It is important to note that any action we take to peg NBT to BKC on either blockchain is a statement that Nu and B&C are working cohesively. This action can be seen as linking the profit and debt of one to the other, depending on the exact protocol of the burn gateway. For the beginning, this is of course already the case as all NSR holders are now BKS holders. Hopefully, BKS holders that are not NSR holders will see the benefit Nu brings from the very beginning with liquidity and burn gateways to help stabilize its BKC, which has no stable history as of yet.