◈◈Bitcredit ◈◈ Migrating to UniQredit◈◈

[shojayxt]

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.

yes so for one block, the pool did not hash.... how does that connect with updating the wallet and cutting off old unsupported wallets?

t
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

Yes, because the network accepts the blocks. But they do not pay masternodes. In the future those blocks won't be accepted (or shouldn't be accepted)

So after block 85,00 (or whatever it is) all my solo blocks will be rejected?

I guess. But bitcreditscc does no testing at all.

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.

[1714831841]

1714831841

[1714831841]

1714831841

[bitcreditscc]

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.

yes so for one block, the pool did not hash.... how does that connect with updating the wallet and cutting off old unsupported wallets?

t
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?

because the clpts rpc solo miner will use the wrong coinbase, e.g. it will not pay masternodes... You could have asked me weeks ago to support MN payments in the miner, but then I had to know how getblocktemplate will work. Obviously, you didn't notice the implications of the update.

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.  

[bitcreditscc]

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.

[NaN_PTS]

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.

yes so for one block, the pool did not hash.... how does that connect with updating the wallet and cutting off old unsupported wallets?

t
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?

because the clpts rpc solo miner will use the wrong coinbase, e.g. it will not pay masternodes... You could have asked me weeks ago to support MN payments in the miner, but then I had to know how getblocktemplate will work. Obviously, you didn't notice the implications of the update.

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.  

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.

[dragos_bdi]

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.

I think is the best way to do it
The problem is that we are near 85000 ...

[NaN_PTS]

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.

I think is the best way to do it
The problem is that we are near 85000 ...

Are you able to fix p2pool? Otherwise it makes no sense to enforce the update. I need two days or so to update the miner.

[bitcreditscc]

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.

I think is the best way to do it
The problem is that we are near 85000 ...

Are you able to fix p2pool? Otherwise it makes no sense to enforce the update. I need two days or so to update the miner.

Interesting comments, what would that prove?

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.

[NaN_PTS]

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.

I think is the best way to do it
The problem is that we are near 85000 ...

Are you able to fix p2pool? Otherwise it makes no sense to enforce the update. I need two days or so to update the miner.

Interesting comments, what would that prove?

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.

You are telling me, that 2 transactions lead to a block size which exceeds the maximum block size of p2pool? I guess not. If you want me to demonstrate it, I could bring p2pool down for an hour in a few hours.

[bitcreditscc]

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.

I think is the best way to do it
The problem is that we are near 85000 ...

Are you able to fix p2pool? Otherwise it makes no sense to enforce the update. I need two days or so to update the miner.

Interesting comments, what would that prove?

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.

You are telling me, that 2 transactions lead to a block size which exceeds the maximum block size of p2pool? I guess not. If you want me to demonstrate it, I could bring p2pool down for an hour in a few hours.

Feel free to try

[hack_]

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.

[bitcreditscc]

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.

on that note there is no looking back, we will be moving forward.

[dragos_bdi]

First block has one transaction leading to a size of 3301 bytes, second just one, 228 bytes.

Code:

20:41:20

getblock "00000568786142d518c55913b158594f1d7c47fdd4857118ed19e58e538dcd4c"


20:41:20

{
"hash" : "00000568786142d518c55913b158594f1d7c47fdd4857118ed19e58e538dcd4c",
"confirmations" : 320,
"size" : 3301,
"height" : 83515,
"version" : 2,
"merkleroot" : "95f64704389503b80d020214937a4cd9c90e6305fe30828817159bfa76401fb9",
"tx" : [
"4efd15af9a2a40f9f98992faf2d8d48f17c893ee6be28d53a03994bc2929a028",
"7df41e578c295f381cb9d9c304b94f4bea318c1bef08ba21e915ba0bddde65f0"
],
"time" : 1428484118,
"nonce" : 152241063,
"BirthdayA" : 45652661,
"BirthdayB" : 29442405,
"bits" : "1e0950ab",
"difficulty" : 0.00041934,
"chainwork" : "0000000000000000000000000000000000000000000000000000000664455a97",
"previousblockhash" : "00000110b0fc6bdf3ddaaa6807d7f201c65a899fc57df36418b8fd34e90e2e27",
"nextblockhash" : "000009a80cb2b4a87be3e51b293d477ef023e7bcac12a07b4cc86a55493dfd39"
}


20:42:07

getblock "000009a80cb2b4a87be3e51b293d477ef023e7bcac12a07b4cc86a55493dfd39"


20:42:07

{
"hash" : "000009a80cb2b4a87be3e51b293d477ef023e7bcac12a07b4cc86a55493dfd39",
"confirmations" : 320,
"size" : 288,
"height" : 83516,
"version" : 2,
"merkleroot" : "f8a1bc2fdcf32cb4c26e7377fe210461d18acc1fdb3aee37ef9d46c5df4f8998",
"tx" : [
"f8a1bc2fdcf32cb4c26e7377fe210461d18acc1fdb3aee37ef9d46c5df4f8998"
],
"time" : 1428484235,
"nonce" : 1175541264,
"BirthdayA" : 33658507,
"BirthdayB" : 36472865,
"bits" : "1e0cbb0b",
"difficulty" : 0.00030683,
"chainwork" : "000000000000000000000000000000000000000000000000000000066459767c",
"previousblockhash" : "00000568786142d518c55913b158594f1d7c47fdd4857118ed19e58e538dcd4c",
"nextblockhash" : "000017451d62bdb2c942d69097c955d24bcd0c2bd51d89ff2cab1bafe182a21f"
}

[shojayxt]

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.

I think is the best way to do it
The problem is that we are near 85000 ...

Are you able to fix p2pool? Otherwise it makes no sense to enforce the update. I need two days or so to update the miner.

Interesting comments, what would that prove?

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.

One could make the argument that the p2pool is part of the ecosystem.

[dragos_bdi]

It will be helpful to have the p2pool log and the debug.log of the wallet to be analyzed ...

[bitcreditscc]

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.

I think is the best way to do it
The problem is that we are near 85000 ...

Are you able to fix p2pool? Otherwise it makes no sense to enforce the update. I need two days or so to update the miner.

Interesting comments, what would that prove?

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.

One could make the argument that the p2pool is part of the ecosystem.

i took it down a sec and increased it's tx/share load to 500kb, lets see what happens.

But overall, in one day, the pool missed 3-5 blocks, i dont see how that is something we should be dramatic about.

we have much bigger fish to fry like messaging and colored coins.

[bitcreditscc]

Let's not forget you people are repeating the same fatal mistake i warned against.

for me to be in charge of the wallet and pools is a bad idea, apart fro the fact that my skills are far from great, it is major centralization.

If i go unplugged for a bit, and something happens, it leaves you all vulnerable. It costs you nothing to run a local p2pool on your server along with your mining wallet.

Guys seriously, we need to decentralize everything. reliance on one piece makes us very very open to problems. In fact, i think we need a port of other pool software.

The one adv of p2pool is that it allows your trust rating to increase unlike other pools.

[dbt1033]

Can't we all just....GET ALONG?

I understand some people might have issues, but let's try to keep our cool guys.

This is a big project.  We are all adults here (hopefully).

[NaN_PTS]

Can't we all just....GET ALONG?

I understand some people might have issues, but let's try to keep our cool guys.

This is a big project.  We are all adults here (hopefully).

I'm trying to solve some issues, but it's hardly possible, if bitcreditscc says that there are no issues... This won't work in the future.
@Bitcreditscc: what does the p2pool log show? I'm using a wallet with 20BCR, but it mostly keeps saying "insufficient funds", if I'm trying to make some small transactions.

[dbt1033]

Can't we all just....GET ALONG?

I understand some people might have issues, but let's try to keep our cool guys.

This is a big project.  We are all adults here (hopefully).

I'm trying to solve some issues, but it's hardly possible, if bitcreditscc says that there are no issues... This won't work in the future.
@Bitcreditscc: what does the p2pool log show? I'm using a wallet with 20BCR, but it mostly keeps saying "insufficient funds", if I'm trying to make some small transactions.

We all appreciate your help and support. 

I guess you're just a incredibly direct person. 

It just seemed like you were getting very angry lol.
 

[NaN_PTS]

Can't we all just....GET ALONG?

I understand some people might have issues, but let's try to keep our cool guys.

This is a big project.  We are all adults here (hopefully).

I'm trying to solve some issues, but it's hardly possible, if bitcreditscc says that there are no issues... This won't work in the future.
@Bitcreditscc: what does the p2pool log show? I'm using a wallet with 20BCR, but it mostly keeps saying "insufficient funds", if I'm trying to make some small transactions.

We all appreciate your help and support. 

I guess you're just a incredibly direct person. 

It just seemed like you were getting very angry lol.
 

Yeah, sorry for that, but I'm telling bitcreditscc that p2pool has a serious issue since weeks. As you might have noticed I'm the only person working on SecureMessaging at the moment. Therefore, I just didn't want it to be released untested. But that happened and other unnecessary errors were included in other releases. This project needs someone with great ideas and someone who makes decisions, but bitcreditscc often seems to ignore my comments. I made the proposal to include the necessary part of the coinbase in getblocktemplate to ease the development of the miner. Well, I never got an answer. I hope that you understand why I'm frustrated.