◈◈Bitcredit ◈◈ Migrating to UniQredit◈◈

[bitcreditscc]

nvidia windows pool miner ?

https://github.com/reorder/momentum-getwork

[1714799870]

1714799870

[1714799870]

1714799870

[hack_]

Pools going down for update, 10 minutes max.

[thelonecrouton]

A bit of a thought was passed to me... wondering what your opinion of it is.

Instead of creating tons of classes of nodes and bloating the code unnecessarily, why not make it such that a BN can only do certain functions when it is above a certain threshold? Meaning that if you have a BN , you can do basic stuff, a BN with 20K can do escrow, a BN with 20K fund and another 50K can do escrow and be a Notary*(just an idea floating around) , a BN with 20K+50K + 130K can be a Bank eg etc and the list goes on.

This is compared to my system where you can only be one of the nodes.... the above system is easier for those with funds..but risks lowering the BN pool we are hoping to increase since that will make up the transaction processors.

Thoughts?

Same thought had occurred to me. People just love rank and status...  

I was thinking of having a sliding scale of BN bid reward based on collateral amount too, with a bias towards 'smaller' smartnodes to encourage more instances of them.

eg 250k BN gets 16 BCR, 50k BN gets 4 BCR? Enough of a delta there to make it worth the extra effort. Maybe something to consider, I'm happy either way though.

Could make the collateral amount function like binary in terms of your available options:
|     |     |     |     |     |     |     |     |
256 128 64  32   16  8     4    2     1K

ie. if you have 128k collateral you could be 1 128k node, or 2 64k nodes, or a 64k and 2 32k nodes, or 4 32k nodes... etc.

[thelonecrouton]

The statistics button still gets stuck - it highlights then when you click on a tab above it it stays highlighted (minor issue)

Easy fix which I never quite get around to. Will do it tomorrow.  

edit: I have unchunkified the sync progress bar, ! never normally see it but was testing everything worked on a clean *buntu 14.10 box. (It did.)

The wiki needs updating I think though as I got an error on execution:
"/usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.8' not found (required by ./bitcredit-qt)"

- fixed with:
sudo add-apt-repository ppa:ubuntu-toolchain-r/test
sudo apt-get update
sudo apt-get install libstdc++6-4.7-dev
sudo apt-get install libstdc++6

[hack_]

Done

[hack_]

A bit of a thought was passed to me... wondering what your opinion of it is.

Instead of creating tons of classes of nodes and bloating the code unnecessarily, why not make it such that a BN can only do certain functions when it is above a certain threshold? Meaning that if you have a BN , you can do basic stuff, a BN with 20K can do escrow, a BN with 20K fund and another 50K can do escrow and be a Notary*(just an idea floating around) , a BN with 20K+50K + 130K can be a Bank eg etc and the list goes on.

This is compared to my system where you can only be one of the nodes.... the above system is easier for those with funds..but risks lowering the BN pool we are hoping to increase since that will make up the transaction processors.

Thoughts?

Same thought had occurred to me. People just love rank and status...  

I was thinking of having a sliding scale of BN bid reward based on collateral amount too, with a bias towards 'smaller' smartnodes to encourage more instances of them.

eg 250k BN gets 16 BCR, 50k BN gets 4 BCR? Enough of a delta there to make it worth the extra effort. Maybe something to consider, I'm happy either way though.

Could make the collateral amount function like binary in terms of your available options:
|     |     |     |     |     |     |     |     |
256 128 64  32   16  8     4    2     1K

ie. if you have 128k collateral you could be 1 128k node, or 2 64k nodes, or a 64k and 2 32k nodes, or 4 32k nodes... etc.

How would the code distinguish and tell other nodes?

[thelonecrouton]

For linux binaries ... http://bitcredits.pw/downloads/

Are you able to package the linux qt binary with the stylesheet.qss and vanilla.qss files? Without them the client is missing the bottom toolbar if they haven't compiled it themselves...     Maybe we can make a little self-extracting zip/tar script to create a basic bitcredit.conf  etc.?

Does the Win version have a desktop icon?

[thelonecrouton]

How would the code distinguish and tell other nodes?

Not my department.  

But I would think via privkey maybe. Privkey begins/ends with an X.. node type A, with a Y... node type B  -  or something like that? The flags could be embedded in there somehow.

[bitcreditscc]

A bit of a thought was passed to me... wondering what your opinion of it is.

Instead of creating tons of classes of nodes and bloating the code unnecessarily, why not make it such that a BN can only do certain functions when it is above a certain threshold? Meaning that if you have a BN , you can do basic stuff, a BN with 20K can do escrow, a BN with 20K fund and another 50K can do escrow and be a Notary*(just an idea floating around) , a BN with 20K+50K + 130K can be a Bank eg etc and the list goes on.

This is compared to my system where you can only be one of the nodes.... the above system is easier for those with funds..but risks lowering the BN pool we are hoping to increase since that will make up the transaction processors.

Thoughts?

Same thought had occurred to me. People just love rank and status...  

I was thinking of having a sliding scale of BN bid reward based on collateral amount too, with a bias towards 'smaller' smartnodes to encourage more instances of them.

eg 250k BN gets 16 BCR, 50k BN gets 4 BCR? Enough of a delta there to make it worth the extra effort. Maybe something to consider, I'm happy either way though.

Could make the collateral amount function like binary in terms of your available options:
|     |     |     |     |     |     |     |     |
256 128 64  32   16  8     4    2     1K

ie. if you have 128k collateral you could be 1 128k node, or 2 64k nodes, or a 64k and 2 32k nodes, or 4 32k nodes... etc.

How would the code distinguish and tell other nodes?

I thin it can be done at the net level , each node type will send a different message

[Bank_sy]

A bit of a thought was passed to me... wondering what your opinion of it is.

Instead of creating tons of classes of nodes and bloating the code unnecessarily, why not make it such that a BN can only do certain functions when it is above a certain threshold? Meaning that if you have a BN , you can do basic stuff, a BN with 20K can do escrow, a BN with 20K fund and another 50K can do escrow and be a Notary*(just an idea floating around) , a BN with 20K+50K + 130K can be a Bank eg etc and the list goes on.

This is compared to my system where you can only be one of the nodes.... the above system is easier for those with funds..but risks lowering the BN pool we are hoping to increase since that will make up the transaction processors.

Thoughts?

Same thought had occurred to me. People just love rank and status...  

I was thinking of having a sliding scale of BN bid reward based on collateral amount too, with a bias towards 'smaller' smartnodes to encourage more instances of them.

eg 250k BN gets 16 BCR, 50k BN gets 4 BCR? Enough of a delta there to make it worth the extra effort. Maybe something to consider, I'm happy either way though.

Could make the collateral amount function like binary in terms of your available options:
|     |     |     |     |     |     |     |     |
256 128 64  32   16  8     4    2     1K

ie. if you have 128k collateral you could be 1 128k node, or 2 64k nodes, or a 64k and 2 32k nodes, or 4 32k nodes... etc.

How would the code distinguish and tell other nodes?

I thin it can be done at the net level , each node type will send a different message

I like this idea. Maybe with this one large bank node can also offer many different services!

If you have 300k you can have 1x50k node, 1x100k node, and 1x150k node OR 1x150k and 3x50k, etc

It makes sense that if you are supporting BCR network with lots of BCR that you can get more BCR and also offer more BCR services.

[bitcreditscc]

I am considering updating our base to Bitcoin 0.11, up from our current 0.10.x

[bitcreditscc]

While I conceptualize Notary nodes, test Escrow Nodes and re-think the client-server relationship for Banking...i am also considering introduction of Lottery Nodes....ie a company on the blockchain that runs a lottery.

Thoughts?

[Bank_sy]

While I conceptualize Notary nodes, test Escrow Nodes and re-think the client-server relationship for Banking...i am also considering introduction of Lottery Nodes....ie a company on the blockchain that runs a lottery.

Thoughts?

That is a great idea, the new wallet keeps crashing when I try and load it.... I am running Windows 8
For more ideas on lottery check out this - https://bitcointalk.org/index.php?topic=1057522.msg11344195#msg11344195

[bitcreditscc]

While I conceptualize Notary nodes, test Escrow Nodes and re-think the client-server relationship for Banking...i am also considering introduction of Lottery Nodes....ie a company on the blockchain that runs a lottery.

Thoughts?

That is a great idea, the new wallet keeps crashing when I try and load it.... I am running Windows 8
For more ideas on lottery check out this - https://bitcointalk.org/index.php?topic=1057522.msg11344195#msg11344195

Seems like a good starting place, but ours will not be miner dependent , rather a BN puts up the winnings and players buy tickets

[bitcreditscc]

Any one wanna try helping us with a new set of graphics for the OP?

Also maybe try a dedit card design?

[dragos_bdi]

For linux binaries ... http://bitcredits.pw/downloads/

Are you able to package the linux qt binary with the stylesheet.qss and vanilla.qss files? Without them the client is missing the bottom toolbar if they haven't compiled it themselves...     Maybe we can make a little self-extracting zip/tar script to create a basic bitcredit.conf  etc.?

Does the Win version have a desktop icon?

Send me the files

[alganonim]

https://mega.co.nz/#!UwxTBLIA!5n3Ssb91bOpKuzVA9ixNftPgQuhd4Ba4hUxGnkpQIL0

Windows Update - final

Thanx

Updated to new files, it worked for the first time, but after closing and opening again, same problem as before - crashed after "Done loading" message, deleting mncache.dat didn't helped.

try removing everything except wallet.dat

Done, even without wallet.dat, pure new empty wallet catalogue and same error, even tried in a a few locations (default appdata and some custom) and run as admin, with upgraded files it worked few times but then after some closing and opening again error returned.

[bitcreditscc]

https://mega.co.nz/#!UwxTBLIA!5n3Ssb91bOpKuzVA9ixNftPgQuhd4Ba4hUxGnkpQIL0

Windows Update - final

Thanx

Updated to new files, it worked for the first time, but after closing and opening again, same problem as before - crashed after "Done loading" message, deleting mncache.dat didn't helped.

try removing everything except wallet.dat

Done, even without wallet.dat, pure new empty wallet catalogue and same error, even tried in a a few locations (default appdata and some custom) and run as admin, with upgraded files it worked few times but then after some closing and opening again error returned.

Very strange, you must delete the mncache.dat everytime it fails. I am working on a update for all that as well as a failsafe that will delete it automatically if it is causing problems.

[thelonecrouton]

I suspect a lot of the segfaulting is timing related. I had endless grief trying to sort the banknode list because even though the table had been fully populated, I could see it there on screen, in the background the wallet was still doing something and when I ran the filter it crashed. Had to put a simple 'if rows>0' in there to make sure that the internals had caught up with the display to stop the filter getting executed before the rest of the thing was ready.

The Bitcoin core wallet is a convoluted mess, if I had a spare 6 months I'd throw the lot of it away and start from scratch. In python. 

[gjhiggins]

The Bitcoin core wallet is a convoluted mess, if I had a spare 6 months I'd throw the lot of it away and start from scratch. In python. 

That's all that's needed for a promising, high-appeal ICO When do we start?

Cheers

Graham