◈◈Bitcredit ◈◈ Migrating to UniQredit◈◈

[tommyj1]

is there any other solo miner?

[thelonecrouton]

Recompiled from git master (up to commit 'df'), deleted everything but my wallet.dat and bitcredit.conf (only 198.52.160.59 and 198.52.160.60 as addnodes) and both local qt (-litemode) and BN daemon seem to be syncing fine. Will update when done. Hopefully.

BN seems synced:

Code:

./bitcredit-cli getinfo
{
    "version" : 301607,
    "protocolversion" : 70008,
    "walletversion" : 60000,
    "balance" : 267918.06360326,
    "darksend_balance" : 0.00000000,
    "blocks" : 107000,
    "timeoffset" : 0,
    "moneysupply" : 14944334.99811231,
    "connections" : 8,
    "proxy" : "",
    "difficulty" : 0.00011261,
    "testnet" : false,
    "keypoololdest" : 1429045624,
    "keypoolsize" : 2,
    "unlocked_until" : 0,
    "paytxfee" : 0.00000000,
    "relayfee" : 0.00001000,
    "errors" : ""
}

addnode=176.126.241.192:9999 if anyone wants to sync from it.

Local qt still catching up. edit: finally caught up and in sync with my BN.

[antonio8]

i have 5 connections, but the client say, no blockchain source available

i use the old blockchain, then the client crash

Windows x64 0.30.16.7c (with blocksize==20MB)

Just downloaded this version and put the litemode in the config.

The wallet will not open. It just force closes at launch. I have tried opening it about 20 times now.

[thelonecrouton]

Looks like chainz forked off at 106629 and bittrex at 106630.

[fairglu]

Attempting a resynchronize for the explorer wallet, I have the following error messages in the log

Code:

2015-05-05 14:16:14 GetSpork::Unknown Spork 1427803200
2015-05-05 14:16:14 CheckBlock() : skipping transaction locking checks
2015-05-05 14:16:14 CheckBlock() : skipping banknode payment checks
2015-05-05 14:16:14 GetSpork::Unknown Spork 1427803200
2015-05-05 14:16:14 CheckBlock() : skipping transaction locking checks
2015-05-05 14:16:14 CheckBlock() : skipping banknode payment checks
2015-05-05 14:16:14 UpdateTip: new best=0006ed39831dec217b8128ba1087bde96f59e9fc98e3adb54d12830f3cd71f00  height=208  log2_work=19.041825  tx=212  date=2014-12-18 17:19:18 progress=0.000669  cache=198
2015-05-05 14:16:14 CreateNewBlock: Failed to detect banknode to pay
2015-05-05 14:16:14 CreateNewBlock(): total size 1000
2015-05-05 14:16:14 ERROR: ContextualCheckBlockHeader : forked chain older than last checkpoint (height 209)

edit: full resynch passed after wiping the whole .bitcredit directory

[thelonecrouton]

Attempting a resynchronize for the explorer wallet, I have the following error messages in the log

Code:

2015-05-05 14:16:14 GetSpork::Unknown Spork 1427803200
2015-05-05 14:16:14 CheckBlock() : skipping transaction locking checks
2015-05-05 14:16:14 CheckBlock() : skipping banknode payment checks
2015-05-05 14:16:14 GetSpork::Unknown Spork 1427803200
2015-05-05 14:16:14 CheckBlock() : skipping transaction locking checks
2015-05-05 14:16:14 CheckBlock() : skipping banknode payment checks
2015-05-05 14:16:14 UpdateTip: new best=0006ed39831dec217b8128ba1087bde96f59e9fc98e3adb54d12830f3cd71f00  height=208  log2_work=19.041825  tx=212  date=2014-12-18 17:19:18 progress=0.000669  cache=198
2015-05-05 14:16:14 CreateNewBlock: Failed to detect banknode to pay
2015-05-05 14:16:14 CreateNewBlock(): total size 1000
2015-05-05 14:16:14 ERROR: ContextualCheckBlockHeader : forked chain older than last checkpoint (height 209)

edit: full resynch passed after wiping the whole .bitcredit directory

Thanks fairglu, chainz explorer back in sync with my local qt client and my BN, anyway.  

[NaN_PTS]

Its all good we will follow your lead, as of 2 hours ago i can not get either wallet to sync with the network.  I will just turn off my miners for the night or send them elsewhere.  One day does not a project make or break.  Will be back tomorrow no worries.  Appreciate your effort and I am certain these glitches will be ironed out in the next rev.  All my wallets at 106630 using the new .7-beta as linked are unable to find the new chain.  Could you post an add node for us to manual add to get on the right fork.

fastest way is to connect to 198.52.160.59 and 198.52.160.60.

Also 198.52.160.64 is on correct chain. I've already alerted exchange rep and block explorer owner.

users who noticed that old miner is not working have already switched back to the pool.

My rationale for this hard fork is as follows:- Transaction limit of 1 MB was not useable for planned future expansion, note, it's not a gimmick like other coins, we really will be using up a lot of space in a block with new security measures and metadata for reversible transactions and other innovations.

This update also forced all blocks to contain BN payments, all users must play by the same basic rules for us to have true consensus.

Two known issues are :-

For some reason Qt only working in litemode
And some icons in cleaned up QT are not showing especially for the tabbed statistics and message pages. We'll look into all this and more. Also trying to figure out a way to shorten overall startup time.

Meanwhile, if you have trouble syncing, just connect to the above mentioned noes using latest build for this link: - Windows x64 0.30.16.7b (with blocksize==20MB)

Source is always up to date

LOL, at least you have found the error in your "very straight forward" code https://github.com/bitcreditscc/bicreditsnew/commit/00513f15c440d983adc833c4bc3da686587a455e. The specification says 20% of the block value goes to BN and not any more. You even increased the payments! Congratulation, you have introduced another hard fork.
Now you have to mention the 10,000,000 BCR premine (or however you call it) and what shall happen to the bank and reserve payments.
I will update the miner as soon as you have corrected your BS, otherwise you would just scam miners and waste my time. Sorry, I've corrected many bugs in the wallet and in p2pool, but you still do no listen to me; you don't even test your own code.

you are just sour that i closed the loophole you were exploiting. You'll note that you've said nothing new if you even followed the thread.

your miner is your own business and i've told you countless times, this project is not predicated on your miner. if you wish to be a part of the process, that is up to you, but don't expect me to give what you say a second look, your attitude stinks.

Well, then why did you promise to obey the specification? Am I wrong with the specification? Why aren't you able to test a release? Your just arrogant and making mostly empty promises. My last warning was ignored, too, and the scenario became reality. Would you have listened to me this time? No. I don't want to have large influence in this project, if you understand this, otherwise this would have happened after the last fork.

for one, that infographic was not done by me. and when that and other issues were realized,  it was resolved that they would be fixed along with the new graphics.

But like i said, you don't follow the thread and only show up to impress your thoughts without catching up. Your motivations are what made me ignore you, which is excatly what was driving you to try and get people back on an unsupported chain.

we can go at this all day and nothing will be resolved. this is a work in progress, and until you start treating it like that, you'll always be complaining.

You're just a liar. I followed the thread, but why should I comment it, if you'll ignore it? Give me a link to a post in this forum that describes the current payouts to BN. We agreed to something different after dragos_bdi's fork (I had nothing to do with that fork), if you can remember. Do you think nobody will notice, if you change the specification as you did with the update https://github.com/bitcreditscc/bicreditsnew/commit/00513f15c440d983adc833c4bc3da686587a455e without notifying users? You made the infographic official and that's your responsibility. I told you that it contradicts the source code and you haven't change neither. The community shouldn't trust you anymore, if you keep your behaviour.

[Bagdar13]

Its all good we will follow your lead, as of 2 hours ago i can not get either wallet to sync with the network.  I will just turn off my miners for the night or send them elsewhere.  One day does not a project make or break.  Will be back tomorrow no worries.  Appreciate your effort and I am certain these glitches will be ironed out in the next rev.  All my wallets at 106630 using the new .7-beta as linked are unable to find the new chain.  Could you post an add node for us to manual add to get on the right fork.

fastest way is to connect to 198.52.160.59 and 198.52.160.60.

Also 198.52.160.64 is on correct chain. I've already alerted exchange rep and block explorer owner.

users who noticed that old miner is not working have already switched back to the pool.

My rationale for this hard fork is as follows:- Transaction limit of 1 MB was not useable for planned future expansion, note, it's not a gimmick like other coins, we really will be using up a lot of space in a block with new security measures and metadata for reversible transactions and other innovations.

This update also forced all blocks to contain BN payments, all users must play by the same basic rules for us to have true consensus.

Two known issues are :-

For some reason Qt only working in litemode
And some icons in cleaned up QT are not showing especially for the tabbed statistics and message pages. We'll look into all this and more. Also trying to figure out a way to shorten overall startup time.

Meanwhile, if you have trouble syncing, just connect to the above mentioned noes using latest build for this link: - Windows x64 0.30.16.7b (with blocksize==20MB)

Source is always up to date

LOL, at least you have found the error in your "very straight forward" code https://github.com/bitcreditscc/bicreditsnew/commit/00513f15c440d983adc833c4bc3da686587a455e. The specification says 20% of the block value goes to BN and not any more. You even increased the payments! Congratulation, you have introduced another hard fork.
Now you have to mention the 10,000,000 BCR premine (or however you call it) and what shall happen to the bank and reserve payments.
I will update the miner as soon as you have corrected your BS, otherwise you would just scam miners and waste my time. Sorry, I've corrected many bugs in the wallet and in p2pool, but you still do no listen to me; you don't even test your own code.

you are just sour that i closed the loophole you were exploiting. You'll note that you've said nothing new if you even followed the thread.

your miner is your own business and i've told you countless times, this project is not predicated on your miner. if you wish to be a part of the process, that is up to you, but don't expect me to give what you say a second look, your attitude stinks.

Well, then why did you promise to obey the specification? Am I wrong with the specification? Why aren't you able to test a release? Your just arrogant and making mostly empty promises. My last warning was ignored, too, and the scenario became reality. Would you have listened to me this time? No. I don't want to have large influence in this project, if you understand this, otherwise this would have happened after the last fork.

for one, that infographic was not done by me. and when that and other issues were realized,  it was resolved that they would be fixed along with the new graphics.

But like i said, you don't follow the thread and only show up to impress your thoughts without catching up. Your motivations are what made me ignore you, which is excatly what was driving you to try and get people back on an unsupported chain.

we can go at this all day and nothing will be resolved. this is a work in progress, and until you start treating it like that, you'll always be complaining.

You're just a liar. I followed the thread, but why should I comment it, if you'll ignore it? Give me a link to a post in this forum that describes the current payouts to BN. We agreed to something different after dragos_bdi's fork (I had nothing to do with that fork), if you can remember. Do you think nobody will notice, if you change the specification as you did with the update https://github.com/bitcreditscc/bicreditsnew/commit/00513f15c440d983adc833c4bc3da686587a455e without notifying users? You made the infographic official and that's your responsibility. I told you that it contradicts the source code and you haven't change neither. The community shouldn't trust you anymore, if you keep your behaviour.

Nan_PTS i just want to say I am very impressed by your skill specifically with your miner and the improvements you have made over 1+ year.  I am also very impressed by your dedication to working on pool/miner functionality with respect to BCR.  Finally, i think its great that you have noticed discrepancies between the specification and the current implementation with the latest release.  This is the kind of watchdog activity that leads to successful opensource programming projects.

That being said I have worked on a number of software projects over the years.  Discrepancies always ALWAYS arise between documentation and implementation for various reasons especially as the complexity, number of people working, and number of releases increases.  These are not necessary malicious in intent, the bcr dev may have tweaked or changed specification and deviated from some posting but this does not mean he is trying to hide or pull a fast on on anyone.  I know of code currently in low earth orbit that has vastly more discrepancies and vastly more at stake than here.  People sometimes just cant keep 100% of everything straight all the time.

BCR dev, your commitment to this project has been commendable, and your interaction with the community better than almost any i have seen.  I understand how hard it can be to tweak code (that is yours) in the presence of outside opinion.  You have a lot of things you want to try out and it is hard to make sure that each update does not "break" the network, as well as herding all of us onto the next protocol without leaving to many people behind or upsetting people and making them want to leave the project.

My opinion is that this is a work in progress, that has some cool new ideas and cool new technologies, those of us committing hash-power or nodes to the network understand this.  Unlike Bitcoin this project can continually update the code base and make stumbling steps forward; vast sums of money are not at stake, nor should they be.  However, when money comes into the picture, and at 2-3k this becomes thousands of dollars for some people, tempers will rise.  This is a hard line to walk especially when it could be perceived that someone is trying to gain the system or get an unfair advantage.(in full disclosure of course i run python scrypts that coin hop when the difficulty is low, i really ran up the score on NEOS, DGB and unitus, so ya people will take advantage of a situation if they can out maneuver a code-base)

So I would ask that we not resort to name calling just yet, both of you have brought up good points and clearly know and ply your craft with skill.   Sometimes messages on forums seem a bit harsher than intended.  This is only one debate, and the first of many to come.  I think it might be time to create a issue/resolution system for such issues for documentation-code-implementation. 

Might I propose we create some sub threads on the main page (or maybe elsewhere) linking to issues (and we could start with this one) where people cleanly lay out a problem and then interaction with the dev for specific issues can be addressed, this way problems can be isolated as well as documented and closed when resolved, while building trust along the way.  I really like they way NaN-PTS clearly used github to demarcate the changes under observation.  This way critical points wont be lost in a 90 page long thread.  I fully expect with continual releases more problems will emerge, and we cant resort to a he-said she-said back and forth every time, i think were all better than that.

[bitcreditscc]

I agree. Either way he has a way of doing things, and i have mine. Maybe we will find middle ground somewhere. After we resolve this minor fork , we will have a lot to discuss.

Allow me to quickly pen my thoughts here

1) Collateral via multi-chain tracking
2) Internal management Money vs Currency
3) Stock trading on the blockchain
4)Fixed money supply management and tracking
5) Multi-token/Colored-token system.
6) Direct Fiat rates (no BTC middleman)


I'll expand on the above as much as i can soon, but these are the chief conceptual issues in my mind. I think some of the concepts may require diagrams.

Let me start with the first

As you all know, P2PL is the first item on the table for banking, though any have asked the question how we will approach the idea of scamers running with funds. Because these concepts are always evolving, we were initially to rely on the huge investment it would take to gain trust. This  however resulted in questions of barriers to entry for newcomers. We had to think deeper and be more innovative. As some of you have seen, if i want to get something done, i may rely on re-purposing existing solutions because their code is tried and tested.

I came up with the following solution that fast tracks some items i had ear-marked for later but solves today's problems:- Basically, you can use coins from another currency as collateral for a loan. I am going to begin work on a separate client that works with our chain but also tracks multiple other chains whose coins can be accepted as collateral. While we cannot support every coin out there we will likely support the top coins in the community as well as those chosen by popular demand. One of the pre-requisites will be that the coin used for collateral must be sufficiently liquid to allow immediate liquidation should there be an issue.

So at time of loan request and approval/denial, the value of your collateral is calculated and if the loan is approved, the system generates an escrow address and sends a tx request. The winning node, automatically sets up an escrow address and sends the address to both parties. It then waits for the funds to enter, then the loan is processed by confirmation message sent to BN.

The system is highly complicated and requires a lot of coding and security. TBH a lot of it is beyond my reach as a coder, i will need a ton of help and this will not be easy.

So i'll take some time and expand on the rest later, but i'd like to make another impetant announcement.

Since the scope of the project is nearly completely defined, i have come to the point where i see no way beyond getting outside help and funding. I am now actively pursuing registering as a company and getting a legal framework put forward, once this is done, I'm putting my face on this project.

[Mario241077]

i have 5 connections, but the client say, no blockchain source available

i use the old blockchain, then the client crash

Windows x64 0.30.16.7c (with blocksize==20MB)

yes i use this version

you use the "b" version, not "c" version ...

Oh thank you, I have not seen it!

[Mario241077]

I can not send coins! Any ideas?

I do not use copy!
I've created a new wallet and all transactions re-imported with a private key!
I have 1000 BCR, but can not even 100 BCR send!
-rescan was unsuccessful!

I know not further !?

[bitcreditscc]

I can not send coins! Any ideas?

I do not use copy!
I've created a new wallet and all transactions re-imported with a private key!
I have 1000 BCR, but can not even 100 BCR send!
-rescan was unsuccessful!

I know not further !?

do get balance,

in this version i tried to get darksend working

[thelonecrouton]

I can not send coins!

The version I am running that I compiled myself did not give me any error when I did a send a while back, but I can't confirm it definitely works yet as block 107254 is taking so bloody long to get solved (30 mins so far) - yet another reason PoW is useless. 

[Mario241077]

I can not send coins! Any ideas?

I do not use copy!
I've created a new wallet and all transactions re-imported with a private key!
I have 1000 BCR, but can not even 100 BCR send!
-rescan was unsuccessful!

I know not further !?

do get balance,

in this version i tried to get darksend working

I still need a moment, my wallet crashes! I Now start a new wallet and do an importing of the private key!

[thelonecrouton]

bitcreditscc, any ideas why block 107254 has so far taken 1hr42mins? I tried to setgenerate true to hurry it on a bit but got a core dump. 

[Mario241077]

I can not send coins! Any ideas?

I do not use copy!
I've created a new wallet and all transactions re-imported with a private key!
I have 1000 BCR, but can not even 100 BCR send!
-rescan was unsuccessful!

I know not further !?

do get balance,

in this version i tried to get darksend working

so get balance show

00:27:31

getbalance


00:27:31

1040.20566120

[Bagdar13]

bitcreditscc, any ideas why block 107254 has so far taken 1hr42mins? I tried to setgenerate true to hurry it on a bit but got a core dump. 

The pools have like 4-5 kh/s. at diff 3k, that should be solved in like 30 seconds ...i think its not on a high diff block so something else is up, as time proceeds i am sure it will illuminate itself.  Also, it seems that the new wallet has fixed the syncing issue of yesterday so that's one down.

[bitcreditscc]

bitcreditscc, any ideas why block 107254 has so far taken 1hr42mins? I tried to setgenerate true to hurry it on a bit but got a core dump. 

The pools have like 4-5 kh/s. at diff 3k, that should be solved in like 30 seconds ...i think its not on a high diff block so something else is up, as time proceeds i am sure it will illuminate itself.  Also, it seems that the new wallet has fixed the syncing issue of yesterday so that's one down.

can you post your getblocktemplate?

[bitcreditscc]

Code:

deploy@localhost:~/bicreditsnew/src$ ./bitcredit-cli getblocktemplate
{
    "capabilities" : [
        "proposal"
    ],
    "version" : 2,
    "previousblockhash" : "000035ab9c21d5c2445f0804ae6a0be668e587e669c19796f2052                                                                                                                                                             8eec90945de",
    "transactions" : [
        {
            "data" : "01000000012b9240b37e5c8c90a50e0dfbec6987efa8ab31b3de20d235                                                                                                                                                             f15996a9e2a16acd000000006a4730440220420523672c9f7a9a63314d37653471c47b22b7402ac0                                                                                                                                                             f290bb3cf4328f31116a02206f011834bf8878e1243e99c0c46658a8740e8d69261166e0632a75a4                                                                                                                                                             f99a9c590121024a7356d0320252b060d74eb1ca9e31975ad91f74eac489cd9cbeafefd2e6d4abfe                                                                                                                                                             ffffff0280969800000000001976a914c1b34a9f8703bf9804411d95158f5ffb19634dbb88ac1b15                                                                                                                                                             5302000000001976a914ffa8ba199bc4ee5f0b7a7c4b08b9356ef217284b88aceca20100",
            "hash" : "aa1b65620ea85de0471ad7de71bd7e6a45800a2ca41c782ede8f31a706                                                                                                                                                             fcbb31",
            "depends" : [
            ],
            "fee" : 225,
            "sigops" : 2
        }
    ],
    "coinbaseaux" : {
        "flags" : "062f503253482f"
    },
    "coinbasevalue" : 5000000225,
    "longpollid" : "000035ab9c21d5c2445f0804ae6a0be668e587e669c19796f20528eec909                                                                                                                                                             45de107256",
    "target" : "0000203691000000000000000000000000000000000000000000000000000000                                                                                                                                                             ",
    "mintime" : 1430858040,
    "mutable" : [
        "time",
        "transactions",
        "prevblock"
    ],
    "noncerange" : "00000000ffffffff",
    "sigoplimit" : 400000,
    "sizelimit" : 400000,
    "curtime" : 1430868267,
    "bits" : "1e203691",
    "height" : 107255,
    "votes" : [
    ],
    "payee" : "5xyD2QYoWoaKMVFLfmvuMs9J1jvWwgP6EY",
    "payee_amount" : 1250000056,
    "banknode_payments" : true,
    "enforce_banknode_payments" : true
}

this means that it's working fine. Likely the pool is letting us down over the transaction issue. Just got in so i'm looking at this now.

At least today i'm working from my dev box.

[Bagdar13]

Code:

deploy@localhost:~/bicreditsnew/src$ ./bitcredit-cli getblocktemplate
{
    "capabilities" : [
        "proposal"
    ],
    "version" : 2,
    "previousblockhash" : "000035ab9c21d5c2445f0804ae6a0be668e587e669c19796f2052                                                                                                                                                             8eec90945de",
    "transactions" : [
        {
            "data" : "01000000012b9240b37e5c8c90a50e0dfbec6987efa8ab31b3de20d235                                                                                                                                                             f15996a9e2a16acd000000006a4730440220420523672c9f7a9a63314d37653471c47b22b7402ac0                                                                                                                                                             f290bb3cf4328f31116a02206f011834bf8878e1243e99c0c46658a8740e8d69261166e0632a75a4                                                                                                                                                             f99a9c590121024a7356d0320252b060d74eb1ca9e31975ad91f74eac489cd9cbeafefd2e6d4abfe                                                                                                                                                             ffffff0280969800000000001976a914c1b34a9f8703bf9804411d95158f5ffb19634dbb88ac1b15                                                                                                                                                             5302000000001976a914ffa8ba199bc4ee5f0b7a7c4b08b9356ef217284b88aceca20100",
            "hash" : "aa1b65620ea85de0471ad7de71bd7e6a45800a2ca41c782ede8f31a706                                                                                                                                                             fcbb31",
            "depends" : [
            ],
            "fee" : 225,
            "sigops" : 2
        }
    ],
    "coinbaseaux" : {
        "flags" : "062f503253482f"
    },
    "coinbasevalue" : 5000000225,
    "longpollid" : "000035ab9c21d5c2445f0804ae6a0be668e587e669c19796f20528eec909                                                                                                                                                             45de107256",
    "target" : "0000203691000000000000000000000000000000000000000000000000000000                                                                                                                                                             ",
    "mintime" : 1430858040,
    "mutable" : [
        "time",
        "transactions",
        "prevblock"
    ],
    "noncerange" : "00000000ffffffff",
    "sigoplimit" : 400000,
    "sizelimit" : 400000,
    "curtime" : 1430868267,
    "bits" : "1e203691",
    "height" : 107255,
    "votes" : [
    ],
    "payee" : "5xyD2QYoWoaKMVFLfmvuMs9J1jvWwgP6EY",
    "payee_amount" : 1250000056,
    "banknode_payments" : true,
    "enforce_banknode_payments" : true
}

this means that it's working fine. Likely the pool is letting us down over the transaction issue. Just got in so i'm looking at this now.

At least today i'm working from my dev box.

this is what I am seeing



{
"blocks" : 107254,
"currentblocksize" : 0,
"currentblocktx" : 0,
"difficulty" : 0.00003234,
"errors" : "",
"genproclimit" : -1,
"networkhashps" : 3330,
"pooledtx" : 0,
"testnet" : false,
"chain" : "main",
"generate" : false,
"hashespermin" : 0
}

CreateNewBlock() : TestBlockValidity failed (code -1) fails as i am now not synced for past 2 hours it says