Topic: ◈◈Bitcredit ◈◈ Migrating to UniQredit◈◈ - page 155. (Read 284545 times)

Quote from: NaN_PTS on May 04, 2015, 11:38:50 PM

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.

bitcreditscc

hero member

Activity: 602

Merit: 501

Quote from: bitcreditscc on May 04, 2015, 10:46:35 PM

Quote from: bitcreditscc on May 04, 2015, 10:46:35 PM

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.

NaN_PTS

newbie

Activity: 49

Merit: 0

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.

bitcreditscc

hero member

Activity: 602

Merit: 501

Quote from: bitcreditscc on May 04, 2015, 09:51:29 PM

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

Bagdar13

member

Activity: 115

Merit: 10

Quote from: NaN_PTS on May 04, 2015, 09:42:02 PM

Quote from: bitcreditscc on May 04, 2015, 09:34:56 PM

Quote from: NaN_PTS on May 04, 2015, 09:42:02 PM

Sorry to bother, but with the new wallet when i try to send coins I keep getting the error that my coins have already been spent. I tried this with a new wallet and with coins mined directly into that wallet. I also tried importing into a different (new clean) wallet using key dump, same result. Do you have any idea why with the new wallet it would say the coins are already spent? Anyone else have this issue?

The new wallet has at least one major bug. To keep the chain running I would recommend to use the last working wallet. 217.244.9.99:8877 is still running the old wallet and the old chain seems to have the majority of the hash power according to the blocks found just before the fork. Currently, the old chain is trying to find block no. 106663.

BELAY THAT!!

There will NOT be any single block accepted that does not conform to the network rules.

Use this wallet:-Windows x64 0.30.16.7b (with blocksize==20MB) as you can see form the p2pools, the active and supported network is alive and kicking.

The chain NAN is pointing at is obsolete and unsupported.

My last comment: Your code is not doing what it is supposed to do. Let the community decide. BTW your code does not match the specification given at the beginning of the thread and the community should know this. You told me that the code would be fixed.

which part?

the community will decide, but either way, your directing people to a fork without checking with me is not how things work. would you take responsibility if something went wrong or would you all of a sudden want me to resolve that?

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.

bitcreditscc

hero member

Activity: 602

Merit: 501

Quote from: bitcreditscc on May 04, 2015, 09:34:56 PM

Quote from: bitcreditscc on May 04, 2015, 09:34:56 PM

Sorry to bother, but with the new wallet when i try to send coins I keep getting the error that my coins have already been spent. I tried this with a new wallet and with coins mined directly into that wallet. I also tried importing into a different (new clean) wallet using key dump, same result. Do you have any idea why with the new wallet it would say the coins are already spent? Anyone else have this issue?

The new wallet has at least one major bug. To keep the chain running I would recommend to use the last working wallet. 217.244.9.99:8877 is still running the old wallet and the old chain seems to have the majority of the hash power according to the blocks found just before the fork. Currently, the old chain is trying to find block no. 106663.

BELAY THAT!!

There will NOT be any single block accepted that does not conform to the network rules.

Use this wallet:-Windows x64 0.30.16.7b (with blocksize==20MB) as you can see form the p2pools, the active and supported network is alive and kicking.

The chain NAN is pointing at is obsolete and unsupported.

My last comment: Your code is not doing what it is supposed to do. Let the community decide. BTW your code does not match the specification given at the beginning of the thread and the community should know this. You told me that the code would be fixed.

which part?

the community will decide, but either way, your directing people to a fork without checking with me is not how things work. would you take responsibility if something went wrong or would you all of a sudden want me to resolve that?

NaN_PTS

newbie

Activity: 49

Merit: 0

https://s-media-cache-ak0.pinimg.com/736x/55/62/f0/5562f0fe75e16c9a06b5cec6ce873b18.jpg

Sorry to bother, but with the new wallet when i try to send coins I keep getting the error that my coins have already been spent. I tried this with a new wallet and with coins mined directly into that wallet. I also tried importing into a different (new clean) wallet using key dump, same result. Do you have any idea why with the new wallet it would say the coins are already spent? Anyone else have this issue?

The new wallet has at least one major bug. To keep the chain running I would recommend to use the last working wallet. 217.244.9.99:8877 is still running the old wallet and the old chain seems to have the majority of the hash power according to the blocks found just before the fork. Currently, the old chain is trying to find block no. 106663.

There will NOT be any single block accepted that does not conform to the network rules.

Use this wallet:-Windows x64 0.30.16.7b (with blocksize==20MB) as you can see form the p2pools, the active and supported network is alive and kicking.

The chain NAN is pointing at is obsolete and unsupported.

My last comment: Your code is not doing what it is supposed to do. Let the community decide. BTW your code does not match the specification given at the beginning of the thread and the community should know this. You told me that the code would be fixed.

bitcreditscc

hero member

Activity: 602

Merit: 501

Sorry to bother, but with the new wallet when i try to send coins I keep getting the error that my coins have already been spent. I tried this with a new wallet and with coins mined directly into that wallet. I also tried importing into a different (new clean) wallet using key dump, same result. Do you have any idea why with the new wallet it would say the coins are already spent? Anyone else have this issue?

The new wallet has at least one major bug. To keep the chain running I would recommend to use the last working wallet. 217.244.9.99:8877 is still running the old wallet and the old chain seems to have the majority of the hash power according to the blocks found just before the fork. Currently, the old chain is trying to find block no. 106663.

There will NOT be any single block accepted that does not conform to the network rules.

Use this wallet:- Windows x64 0.30.16.7c (with blocksize==20MB) as you can see form the p2pools, the active and supported network is alive and kicking.

The chain NAN is pointing at is obsolete and unsupported.

NaN_PTS

newbie

Activity: 49

Merit: 0