Topic: ◈◈Bitcredit ◈◈ Migrating to UniQredit◈◈ - page 177. (Read 284545 times)
Heated discussion, dos threats, ha what next? Dev, cut off the old ones. No way i will setup a node if i don't get paid for it.
Are you kidding me? I saw the code AFTER the update. I cannot look at all changes you made and I discovered many bugs. I don't know how darkcoin/dash works, sry. Read the forum about the getblocktemplate bug or the p2pool bug. Just test your copy and pasted code before releasing it. If you post further BS, I'll post some conversations between me and you.
Just make an announcement, when to update the wallet. This time point has to be at least 1 week in the future, so that it is possible to do at least some basic testing and the exchanges have time to update. I cannot update the miner all the time because of your broken updates. I simply do not have enough time to do that.
EDIT: btw. I would pay MN, but I'm tired of your broken updates and your broken promises. It's best to have a developing branch and test a release version BEFORE release.
Just make an announcement, when to update the wallet. This time point has to be at least 1 week in the future, so that it is possible to do at least some basic testing and the exchanges have time to update. I cannot update the miner all the time because of your broken updates. I simply do not have enough time to do that.
EDIT: btw. I would pay MN, but I'm tired of your broken updates and your broken promises. It's best to have a developing branch and test a release version BEFORE release.
I think is the best way to do it
The problem is that we are near 85000 ...
Interesting comments, what would that prove?
Quote
Are you able to fix p2pool?
Again i do not see how that relates to a wallet update. p2pool works as it should. if we see the need we will increase the size it can handle a little more .
As for miner update, that is solely up to you as that is your domain. My area is ensuring that everyone is running the right wallet version and all aspects of the ecosystem support each other.
Feel free to try
Are you kidding me? I saw the code AFTER the update. I cannot look at all changes you made and I discovered many bugs. I don't know how darkcoin/dash works, sry. Read the forum about the getblocktemplate bug or the p2pool bug. Just test your copy and pasted code before releasing it. If you post further BS, I'll post some conversations between me and you.
Just make an announcement, when to update the wallet. This time point has to be at least 1 week in the future, so that it is possible to do at least some basic testing and the exchanges have time to update. I cannot update the miner all the time because of your broken updates. I simply do not have enough time to do that.
EDIT: btw. I would pay MN, but I'm tired of your broken updates and your broken promises. It's best to have a developing branch and test a release version BEFORE release.
Just make an announcement, when to update the wallet. This time point has to be at least 1 week in the future, so that it is possible to do at least some basic testing and the exchanges have time to update. I cannot update the miner all the time because of your broken updates. I simply do not have enough time to do that.
EDIT: btw. I would pay MN, but I'm tired of your broken updates and your broken promises. It's best to have a developing branch and test a release version BEFORE release.
I think is the best way to do it
The problem is that we are near 85000 ...
Interesting comments, what would that prove?
Quote
Are you able to fix p2pool?
Again i do not see how that relates to a wallet update. p2pool works as it should. if we see the need we will increase the size it can handle a little more .
As for miner update, that is solely up to you as that is your domain. My area is ensuring that everyone is running the right wallet version and all aspects of the ecosystem support each other.
Are you kidding me? I saw the code AFTER the update. I cannot look at all changes you made and I discovered many bugs. I don't know how darkcoin/dash works, sry. Read the forum about the getblocktemplate bug or the p2pool bug. Just test your copy and pasted code before releasing it. If you post further BS, I'll post some conversations between me and you.
Just make an announcement, when to update the wallet. This time point has to be at least 1 week in the future, so that it is possible to do at least some basic testing and the exchanges have time to update. I cannot update the miner all the time because of your broken updates. I simply do not have enough time to do that.
EDIT: btw. I would pay MN, but I'm tired of your broken updates and your broken promises. It's best to have a developing branch and test a release version BEFORE release.
Just make an announcement, when to update the wallet. This time point has to be at least 1 week in the future, so that it is possible to do at least some basic testing and the exchanges have time to update. I cannot update the miner all the time because of your broken updates. I simply do not have enough time to do that.
EDIT: btw. I would pay MN, but I'm tired of your broken updates and your broken promises. It's best to have a developing branch and test a release version BEFORE release.
I think is the best way to do it
The problem is that we are near 85000 ...
Interesting comments, what would that prove?
Quote
Are you able to fix p2pool?
Again i do not see how that relates to a wallet update. p2pool works as it should. if we see the need we will increase the size it can handle a little more .
As for miner update, that is solely up to you as that is your domain. My area is ensuring that everyone is running the right wallet version and all aspects of the ecosystem support each other.
Are you kidding me? I saw the code AFTER the update. I cannot look at all changes you made and I discovered many bugs. I don't know how darkcoin/dash works, sry. Read the forum about the getblocktemplate bug or the p2pool bug. Just test your copy and pasted code before releasing it. If you post further BS, I'll post some conversations between me and you.
Just make an announcement, when to update the wallet. This time point has to be at least 1 week in the future, so that it is possible to do at least some basic testing and the exchanges have time to update. I cannot update the miner all the time because of your broken updates. I simply do not have enough time to do that.
EDIT: btw. I would pay MN, but I'm tired of your broken updates and your broken promises. It's best to have a developing branch and test a release version BEFORE release.
Just make an announcement, when to update the wallet. This time point has to be at least 1 week in the future, so that it is possible to do at least some basic testing and the exchanges have time to update. I cannot update the miner all the time because of your broken updates. I simply do not have enough time to do that.
EDIT: btw. I would pay MN, but I'm tired of your broken updates and your broken promises. It's best to have a developing branch and test a release version BEFORE release.
I think is the best way to do it
The problem is that we are near 85000 ...
Are you kidding me? I saw the code AFTER the update. I cannot look at all changes you made and I discovered many bugs. I don't know how darkcoin/dash works, sry. Read the forum about the getblocktemplate bug or the p2pool bug. Just test your copy and pasted code before releasing it. If you post further BS, I'll post some conversations between me and you.
Just make an announcement, when to update the wallet. This time point has to be at least 1 week in the future, so that it is possible to do at least some basic testing and the exchanges have time to update. I cannot update the miner all the time because of your broken updates. I simply do not have enough time to do that.
EDIT: btw. I would pay MN, but I'm tired of your broken updates and your broken promises. It's best to have a developing branch and test a release version BEFORE release.
Just make an announcement, when to update the wallet. This time point has to be at least 1 week in the future, so that it is possible to do at least some basic testing and the exchanges have time to update. I cannot update the miner all the time because of your broken updates. I simply do not have enough time to do that.
EDIT: btw. I would pay MN, but I'm tired of your broken updates and your broken promises. It's best to have a developing branch and test a release version BEFORE release.
I think is the best way to do it
The problem is that we are near 85000 ...
look at the pool, no crash 
New work for worker! Difficulty: 0.000001 Share difficulty: 0.000022 Total block value: 50.020000 BCR including 2 transactions
Also i don't get your argument against cutting out old clients. what relevance do they have to p2pool?
Look at the screen shot I've posted. The hashrate went to zero. New work for worker! Difficulty: 0.000001 Share difficulty: 0.000022 Total block value: 50.020000 BCR including 2 transactions
Also i don't get your argument against cutting out old clients. what relevance do they have to p2pool?
yes so for one block, the pool did not hash.... how does that connect with updating the wallet and cutting off old unsupported wallets?
WTF? p2pool does not work if any transaction is included in a block. If you cut out the solo miners with 0.30.14, no one will include the transactions into the chain. Or an attacker will include his transactions. That was just a demonstration. One can DOS p2pool for hours.
and why can they not solo mine with 0.30.16.4?
you have known about these changes far much longer than a week, in fact you saw the code long before anyone else knew exactly what i was working on.
there is just no good reason to keep the old wallets.
Just make an announcement, when to update the wallet. This time point has to be at least 1 week in the future, so that it is possible to do at least some basic testing and the exchanges have time to update. I cannot update the miner all the time because of your broken updates. I simply do not have enough time to do that.
EDIT: btw. I would pay MN, but I'm tired of your broken updates and your broken promises. It's best to have a developing branch and test a release version BEFORE release.
That's why I asked about a testnet some time ago.
This is simply a push to get everyone on the right wallet, i have asked time and again, why I should allow old clients to exist on the network.
I disabled code that would have cut them off right off the bat to avoid network shock and to allow transition time. that time is over.
The real issue here is not about testnets or anything like that. I am saying that everyone should start using the new wallet, those who are against it, are doing so because they do not wish to pay MNs.
look at the pool, no crash
New work for worker! Difficulty: 0.000001 Share difficulty: 0.000022 Total block value: 50.020000 BCR including 2 transactions
Also i don't get your argument against cutting out old clients. what relevance do they have to p2pool?
Look at the screen shot I've posted. The hashrate went to zero. New work for worker! Difficulty: 0.000001 Share difficulty: 0.000022 Total block value: 50.020000 BCR including 2 transactions
Also i don't get your argument against cutting out old clients. what relevance do they have to p2pool?
yes so for one block, the pool did not hash.... how does that connect with updating the wallet and cutting off old unsupported wallets?
WTF? p2pool does not work if any transaction is included in a block. If you cut out the solo miners with 0.30.14, no one will include the transactions into the chain. Or an attacker will include his transactions. That was just a demonstration. One can DOS p2pool for hours.
and why can they not solo mine with 0.30.16.4?
you have known about these changes far much longer than a week, in fact you saw the code long before anyone else knew exactly what i was working on.
there is just no good reason to keep the old wallets.
look at the pool, no crash
New work for worker! Difficulty: 0.000001 Share difficulty: 0.000022 Total block value: 50.020000 BCR including 2 transactions
Also i don't get your argument against cutting out old clients. what relevance do they have to p2pool?
Look at the screen shot I've posted. The hashrate went to zero. New work for worker! Difficulty: 0.000001 Share difficulty: 0.000022 Total block value: 50.020000 BCR including 2 transactions
Also i don't get your argument against cutting out old clients. what relevance do they have to p2pool?
yes so for one block, the pool did not hash.... how does that connect with updating the wallet and cutting off old unsupported wallets?
WTF? p2pool does not work if any transaction is included in a block. If you cut out the solo miners with 0.30.14, no one will include the transactions into the chain. Or an attacker will include his transactions. That was just a demonstration. One can DOS p2pool for hours.
and why can they not solo mine with 0.30.16.4?
I am solo mining with 0.30.16.4b and finding blocks
So after block 85,00 (or whatever it is) all my solo blocks will be rejected?
That's why I asked about a testnet some time ago.
Have you setup a testnet to test the functions of this coin? I have read through the thread and didn't see any reference to one. If not I think you should. Thinking of taking a position in this coin but am still on the fence.
look at the pool, no crash
New work for worker! Difficulty: 0.000001 Share difficulty: 0.000022 Total block value: 50.020000 BCR including 2 transactions
Also i don't get your argument against cutting out old clients. what relevance do they have to p2pool?
Look at the screen shot I've posted. The hashrate went to zero. New work for worker! Difficulty: 0.000001 Share difficulty: 0.000022 Total block value: 50.020000 BCR including 2 transactions
Also i don't get your argument against cutting out old clients. what relevance do they have to p2pool?
yes so for one block, the pool did not hash.... how does that connect with updating the wallet and cutting off old unsupported wallets?
WTF? p2pool does not work if any transaction is included in a block. If you cut out the solo miners with 0.30.14, no one will include the transactions into the chain. Or an attacker will include his transactions. That was just a demonstration. One can DOS p2pool for hours.
and why can they not solo mine with 0.30.16.4?
I am solo mining with 0.30.16.4b and finding blocks
So after block 85,00 (or whatever it is) all my solo blocks will be rejected?
look at the pool, no crash
New work for worker! Difficulty: 0.000001 Share difficulty: 0.000022 Total block value: 50.020000 BCR including 2 transactions
Also i don't get your argument against cutting out old clients. what relevance do they have to p2pool?
Look at the screen shot I've posted. The hashrate went to zero. New work for worker! Difficulty: 0.000001 Share difficulty: 0.000022 Total block value: 50.020000 BCR including 2 transactions
Also i don't get your argument against cutting out old clients. what relevance do they have to p2pool?
yes so for one block, the pool did not hash.... how does that connect with updating the wallet and cutting off old unsupported wallets?
WTF? p2pool does not work if any transaction is included in a block. If you cut out the solo miners with 0.30.14, no one will include the transactions into the chain. Or an attacker will include his transactions. That was just a demonstration. One can DOS p2pool for hours.
and why can they not solo mine with 0.30.16.4?
I am solo mining with 0.30.16.4b and finding blocks
So after block 85,00 (or whatever it is) all my solo blocks will be rejected?
look at the pool, no crash
New work for worker! Difficulty: 0.000001 Share difficulty: 0.000022 Total block value: 50.020000 BCR including 2 transactions
Also i don't get your argument against cutting out old clients. what relevance do they have to p2pool?
Look at the screen shot I've posted. The hashrate went to zero. New work for worker! Difficulty: 0.000001 Share difficulty: 0.000022 Total block value: 50.020000 BCR including 2 transactions
Also i don't get your argument against cutting out old clients. what relevance do they have to p2pool?
yes so for one block, the pool did not hash.... how does that connect with updating the wallet and cutting off old unsupported wallets?
WTF? p2pool does not work if any transaction is included in a block. If you cut out the solo miners with 0.30.14, no one will include the transactions into the chain. Or an attacker will include his transactions. That was just a demonstration. One can DOS p2pool for hours.
and why can they not solo mine with 0.30.16.4?
I am solo mining with 0.30.16.4b and finding blocks
I am having trouble getting the wallet(0.30.16.) to work on my new machine. No Block Source Available - 4 days behind. I have the same version installed on another machine and it is working fine. Any help would be appreciated.
look at the pool, no crash
New work for worker! Difficulty: 0.000001 Share difficulty: 0.000022 Total block value: 50.020000 BCR including 2 transactions
Also i don't get your argument against cutting out old clients. what relevance do they have to p2pool?
Look at the screen shot I've posted. The hashrate went to zero. New work for worker! Difficulty: 0.000001 Share difficulty: 0.000022 Total block value: 50.020000 BCR including 2 transactions
Also i don't get your argument against cutting out old clients. what relevance do they have to p2pool?
yes so for one block, the pool did not hash.... how does that connect with updating the wallet and cutting off old unsupported wallets?
WTF? p2pool does not work if any transaction is included in a block. If you cut out the solo miners with 0.30.14, no one will include the transactions into the chain. Or an attacker will include his transactions. That was just a demonstration. One can DOS p2pool for hours.
and why can they not solo mine with 0.30.16.4?
look at the pool, no crash
New work for worker! Difficulty: 0.000001 Share difficulty: 0.000022 Total block value: 50.020000 BCR including 2 transactions
Also i don't get your argument against cutting out old clients. what relevance do they have to p2pool?
Look at the screen shot I've posted. The hashrate went to zero. New work for worker! Difficulty: 0.000001 Share difficulty: 0.000022 Total block value: 50.020000 BCR including 2 transactions
Also i don't get your argument against cutting out old clients. what relevance do they have to p2pool?
yes so for one block, the pool did not hash.... how does that connect with updating the wallet and cutting off old unsupported wallets?
WTF? p2pool does not work if any transaction is included in a block. If you cut out the solo miners with 0.30.14, no one will include the transactions into the chain. Or an attacker will include his transactions. That was just a demonstration. One can DOS p2pool for hours.
and why can they not solo mine with 0.30.16.4?
I am solo mining with 0.30.16.4b and finding blocks
look at the pool, no crash
New work for worker! Difficulty: 0.000001 Share difficulty: 0.000022 Total block value: 50.020000 BCR including 2 transactions
Also i don't get your argument against cutting out old clients. what relevance do they have to p2pool?
Look at the screen shot I've posted. The hashrate went to zero. New work for worker! Difficulty: 0.000001 Share difficulty: 0.000022 Total block value: 50.020000 BCR including 2 transactions
Also i don't get your argument against cutting out old clients. what relevance do they have to p2pool?
yes so for one block, the pool did not hash.... how does that connect with updating the wallet and cutting off old unsupported wallets?
WTF? p2pool does not work if any transaction is included in a block. If you cut out the solo miners with 0.30.14, no one will include the transactions into the chain. Or an attacker will include his transactions. That was just a demonstration. One can DOS p2pool for hours.
and why can they not solo mine with 0.30.16.4? There is no way i will let those clients continue on this network . there is just no real reason to keep old client, worse off they are working on a different set of rules than the rest.
Everyone must upgrade and keep up with supported client and protocol. those old client will cause massive forking at block 85000, their owners just need to update.
look at the pool, no crash
New work for worker! Difficulty: 0.000001 Share difficulty: 0.000022 Total block value: 50.020000 BCR including 2 transactions
Also i don't get your argument against cutting out old clients. what relevance do they have to p2pool?
Look at the screen shot I've posted. The hashrate went to zero. New work for worker! Difficulty: 0.000001 Share difficulty: 0.000022 Total block value: 50.020000 BCR including 2 transactions
Also i don't get your argument against cutting out old clients. what relevance do they have to p2pool?
yes so for one block, the pool did not hash.... how does that connect with updating the wallet and cutting off old unsupported wallets?
WTF? p2pool does not work if any transaction is included in a block. If you cut out the solo miners with 0.30.14, no one will include the transactions into the chain. Or an attacker will include his transactions. That was just a demonstration. One can DOS p2pool for hours.
look at the pool, no crash
New work for worker! Difficulty: 0.000001 Share difficulty: 0.000022 Total block value: 50.020000 BCR including 2 transactions
Also i don't get your argument against cutting out old clients. what relevance do they have to p2pool?
Look at the screen shot I've posted. The hashrate went to zero. New work for worker! Difficulty: 0.000001 Share difficulty: 0.000022 Total block value: 50.020000 BCR including 2 transactions
Also i don't get your argument against cutting out old clients. what relevance do they have to p2pool?
yes so for one block, the pool did not hash.... how does that connect with updating the wallet and cutting off old unsupported wallets?
look at the pool, no crash
New work for worker! Difficulty: 0.000001 Share difficulty: 0.000022 Total block value: 50.020000 BCR including 2 transactions
Also i don't get your argument against cutting out old clients. what relevance do they have to p2pool?
Look at the screen shot I've posted. The hashrate went to zero. New work for worker! Difficulty: 0.000001 Share difficulty: 0.000022 Total block value: 50.020000 BCR including 2 transactions
Also i don't get your argument against cutting out old clients. what relevance do they have to p2pool?
https://www.dropbox.com/s/qa92qcgjgf9tl1b/hashrate.png?dl=0
If old clients are cut out, then exchanges won't work any more because they most likely use the old client. Furthermore, p2pool does not include any transactions into blocks and my miner does not work with the new wallet. Therefore, the network will be stuck. If you do not communicate with people, then they cannot adopt to changes. Or did you tell me, how the coinbase has to look like or how to deal with future changes? No, I stumbled across the new coinbase when I was trying to figure out what was wrong with 0.30.16. I do not even know, why I'm helping you, when you never listen to me.
Jump to: