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

It is not right. P2pools must operate in one p2p network.
Now the has increased difficulty of the coin:
Greatly reducing the chance to get a block in solo.
I return parameters, the problem is not in my pool.

Best.
Now, even if there is a problem with p2pool.website and bcrp2pool.website, there are other 2 pools to maintain active the network !
This I call decentralization

The first 3 blocks was ok http://crypto.office-on-the.net:8776/static/

No, it shall not affect
I disabled my node from p2p networks.
I check how it works autonomously.

Yes, it's the last version.
Maybe because you do not use DB4.8 as DB support ?

I compiled the latest version of the wallet:


Is it the latest version?

17 banknodes already

Although the order book does not look briliant


I wonder who is selling those thousands all the time. Do we know who is no.2 wallet?

Thanks mate Appreciate that

Win binary is in OP. List of Banknodes, which you can use if you need to: https://chainz.cryptoid.info/bcr/masternodes.dws  (detailed list tab)

Is that the latest windows wallet? Because that's what I'm going to need is the latest windows wallet and nodes for this coin

The latest master builds very stable for me. I am going to host a node for it soon.

Kind of regretting giving up on this coin as early as I did in the beginning because I was having so much trouble with the wallet in the beginning but very nice to see you achieving success Dev I have the utmost respect for you and your coin project and wish you the best of luck I think I may get back into this coin if someone can point me to the nearest updated wallet version and a working .conf file for that wallet Cheers

Hey thanks for clearing that up. I have no idea who owns that pool; but I do have a question if you don't mind.  How did that orphan manage to stall the entire network for so many hours?

Thanks,
[/quote]

First of all, I do not intend to start an argue on this manner.
Second, sawa, the problem start from your pool. Why? I will try to explain in a few words after.
Third, my pool was not the problem, I started the pool when I saw that the network stopped.

Pre:
Now, there are only two possibilities to mine Bitcredits. First, using the wallet, second, using the NaN clpts miner v2.1 or pts-getwork (3 times slower), with p2pool fork made by bitcreditscc.
There is no solominer available, or other type of pools that can sustain the network.

Synopsis:
On sawa pool, was found aprox. 30-40 "orphan" blocks.
My first guess was that you don't update the wallet to last version that enforce the BN payments.
Second guess, is that was a problem in communication with other 2 p2pools (bcrp2pool.website and p2pool.website) because on the list of "found" blocks, only on your pool was a long list of 116502 orphan blocks found and not on the other 2.
Third guess, it's a problem on p2pool code and/or wallet code, that when a block is rejected by the wallet (see the first quote, "Invalid Chain Found") the p2pool see this as "Orphan", and this is wrong. An "orphan" block it is one that is found and accepted by the wallet, but not by the network because someone, a little bit faster, submitted a valid block. So p2pool try to request work and find 116503, even that 116502 it's not found, it's not orphan but was rejected.

ToDo:
Sawa, check to see if you are running the last version of the wallet.
Bitcreditscc, check to see, if you have time, why the p2pool report the block even if it's "Invalid Chain Found" by the wallet.

Sawa, I know very well how to configure the p2pool. The reasons that you exposed are valid in a stable and muti-mining possibilities, but not on the current state of the coin.
Putting my p2pool on the network with other p2pools will not strengthen the network, but will weaken the network, because there are no other viable options to mine.
Because of the reasons that I wrote up, I will maintain my p2pool of the network and I'm sure that this is a good decision.
And to close, when you say that the "problem" was created by my p2pool, write and the reasons. Otherwise, everything is only a "story". I like some technical "why's", not a technical howto add a p2pool on the network with other p2pools.

Thanks !
[/quote]

Just wanted to say that was a great Synopsis, I was trying to piece it together myself but could not, any activity constructed in this positive manner only betters the community in my opinion.  I am always of the opinion that mistakes will be made and bugs in code will be found, that's just the nature of an evolving system.  I don't think anyone should take offence if someone finds a bug as long as it is done in a respectful manner.  I am highly impressed with the respect that you have for other peoples work, i believe this discussion will and should continue in such a productive manner. Good on all of you.

Have a great day

First of all, I do not intend to start an argue on this manner.
Second, sawa, the problem start from your pool. Why? I will try to explain in a few words after.
Third, my pool was not the problem, I started the pool when I saw that the network stopped.

Pre:
Now, there are only two possibilities to mine Bitcredits. First, using the wallet, second, using the NaN clpts miner v2.1 or pts-getwork (3 times slower), with p2pool fork made by bitcreditscc.
There is no solominer available, or other type of pools that can sustain the network.

Synopsis:
On sawa pool, was found aprox. 30-40 "orphan" blocks.
My first guess was that you don't update the wallet to last version that enforce the BN payments.
Second guess, is that was a problem in communication with other 2 p2pools (bcrp2pool.website and p2pool.website) because on the list of "found" blocks, only on your pool was a long list of 116502 orphan blocks found and not on the other 2.
Third guess, it's a problem on p2pool code and/or wallet code, that when a block is rejected by the wallet (see the first quote, "Invalid Chain Found") the p2pool see this as "Orphan", and this is wrong. An "orphan" block it is one that is found and accepted by the wallet, but not by the network because someone, a little bit faster, submitted a valid block. So p2pool try to request work and find 116503, even that 116502 it's not found, it's not orphan but was rejected.

ToDo:
Sawa, check to see if you are running the last version of the wallet.
Bitcreditscc, check to see, if you have time, why the p2pool report the block even if it's "Invalid Chain Found" by the wallet.

Sawa, I know very well how to configure the p2pool. The reasons that you exposed are valid in a stable and muti-mining possibilities, but not on the current state of the coin.
Putting my p2pool on the network with other p2pools will not strengthen the network, but will weaken the network, because there are no other viable options to mine.
Because of the reasons that I wrote up, I will maintain my p2pool of the network and I'm sure that this is a good decision.
And to close, when you say that the "problem" was created by my p2pool, write and the reasons. Otherwise, everything is only a "story". I like some technical "why's", not a technical howto add a p2pool on the network with other p2pools.

Thanks !

I'm no fan of C either.  Header files are an abomination and whoever invented them should be beaten with fiery rattlesnakes.

i have a super massive headache, likely caused by too much screen time or the new round of medicine. taking the night off and likely most of the day tomorrow

hangouts will be the easiest way to contact me

Hey thanks for clearing that up. I have no idea who owns that pool; but I do have a question if you don't mind.  How did that orphan manage to stall the entire network for so many hours?

Thanks,

When I went to college in 2001; they made me do it in C...so I could know the pain of malloc and char* arrays...fuck strings.  Then senior year they said you can have C++ and dynamic memory structures that you don't have to code yourself, and we were great-full to the merciful c++ gods for the vector and the map.

C++ was designed by fucking idiots. 

It's not a problem, it's orphan.
The problem is created by node: http://bitcredits.pw:8776/static/
This node has no peers, probably it was specially configured to work autonomously.
http://bitcredits.pw:8776/peer_addresses = ""

So how other pools connected to p2p network and their speed is faster, they get the most of blocks.
If you are an owner of this node, please connect to others.
Stop the pool, delete .../p2pool-bcr/data directory (with all content), delete *.pyc files and change next parameters in file .../p2pool-bcr/p2pool/networks/bitcredit.py:
/* See the source code on GitHub: https://github.com/bitcreditscc/p2pool */
By doing so you will strengthen the p2p network and reduce the number of orphans.