Topic: ◈◈Bitcredit ◈◈ Migrating to UniQredit◈◈ - page 57. (Read 284526 times)

?

Cheers

Graham

I am going to withdraw the offer to bitcoin alts to absorb them. Instead, i'd like to create a two pronged approach to providing easy fiat/OTC purchase of BCR as follows:-

3 million BCR goes into 30000 accounts , all multisig 2 of 2, namely one master key and 30000 client keys. These will be sold for fiat only via website , accepting visa , wire and/or western union.

The credits will have additional rules as follows :-

Redemption before a specific date of our choosing will result in the total coins being reduced ie instead of receiving 1000 BCR, early redemption will get X % less calculated based on time remaining. A redemption within the maturity stage will result in 1000 BCR + default increase in trust rating. We also give a final redemption date, which if it passes will result in all keys expiring.

What this does is allow interested parties to quickly buy BCR online without need for going through BTC exchanges or the overall hassles people face now to reach us. The other batch of 3 mill will be held to see the success of this project, should it work, we use the rest, or if we prefer we can use it to make physical scratch cards that users can to get more people in their locales/work places interested.

The second is mostly just a request for funds, i'd like to raise 10 BTC so i can hire coders to help me resolve the rather large to do list, review code, remove legacy material, bring in some SPV clients and finally finance creation of the above mentioned website.

Thoughts ?

Indeed!!!!!  glad you could see it

I just finished generating some custom addresses for bidding and have added them to the client, update will be pushed in a short while. Hopefully we'll see people start to take up the jobs and we can get some work done.

I have two major proposals i am working on , will give an overview in the next post. Opinions welcomed 

it's a combo of bad math and bad code, i intend to phase out the bank and reserve in favour of a more flexible system. that will put the payout to 29750 , far more like originally intended. I am waiting on a vanity instance to get a new address , then i'll push the last bits of the latest version (0.30.17.

the bid clearing issue will be resolved in the next update

i see my bid coins, thanks! some small .47BCRs and one big block of 1356.

Confusion:
the bidtracker still shows the balances in the wallet of like .079BTC im assuming its just looking up the btc balance of the bid address. thiswill be confusing to tell how much has been bid

*edit oops looks like this is noticed above. and noted below there should be a solution in the next release.

question though..

who is holding multisig keys?
will the officers be holding them once elected, or is it random banknodes or bitcreditscc?

Me too, amount looks about right.   

Bids don't seem to have been reset / cleaned out of the files though, hopefully coming update sorts that out.

Looks like the BN that block got ~239 BCR, don't know it this will be constant, but seems like the BCR distributed to bidders is going to be about 23750 BCR per superblock after the grants / miner / BN / bnk+dof+mof+sof+tof.

https://github.com/bitcoin/bitcoin/pull/1453/files

though you may want to read this first :- http://bitcoin-development.narkive.com/IK0LYNyG/bitcoin-development-the-legal-risks-of-auto-updating-wallet-software-custodial-relationships

  I was thinking about that yesterday ... ROLF
For that, you must have a launcher that checks for new updates ...

How do you as a user feel about optional automatic updates?

great, final fixes for new update will be up on the git in the hour.

I did receive the payments for my bids ...

will add assets dir to makefile includes, should be on the git in a bit

No chance compiling on windows mingw because of path problem. Even if I include both, util.h and compat.h, one of them has other includes that are not found.

I was under the impression you can not convert a compressed private key into an uncompressed private key. this is from some old research I did, but I'm not an expert. @ proletariat @ bitcreditscc

looks like thats for public keys
https://bitcointalksearch.org/topic/compressed-to-uncompressed-public-keys-c-php-or-online-850011

if this is an issue maybe we could have a dropdown for wallet type key was taken from and a converter built into the wallet

the header

...add to where in coinspark.h or coinspark.c

It's a windows issue then, just add #include "util.h" and "compat.h", should resolve that for you.

Windows 7 32 bit. With the previous master no pr0blem to compile

what system are you building on?

Compiling the new master. There is error

In file included from assets/coinspark.c:26:0:
assets/coinspark.h:92:9: error: unknown type name 'int64_t'
 typedef int64_t CoinSparkSatoshiQty;
         ^
assets/coinspark.h:93:9: error: unknown type name 'int64_t'
 typedef int64_t CoinSparkAssetQty;
         ^
assets/coinspark.h:94:9: error: unknown type name 'int32_t'
 typedef int32_t CoinSparkIOIndex;
         ^
assets/coinspark.h:95:9: error: unknown type name 'int32_t'
 typedef int32_t CoinSparkAddressFlags;
         ^
assets/coinspark.h:96:9: error: unknown type name 'int64_t'
 typedef int64_t CoinSparkPaymentRef;
         ^
assets/coinspark.h:105:5: error: unknown type name 'int16_t'
     int16_t qtyMantissa;
     ^
assets/coinspark.h:106:5: error: unknown type name 'int16_t'
     int16_t qtyExponent;
     ^
assets/coinspark.h:107:5: error: unknown type name 'int16_t'
     int16_t chargeFlatMantissa;
     ^
assets/coinspark.h:108:5: error: unknown type name 'int16_t'
     int16_t chargeFlatExponent;
     ^
.....