-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
raise LateEnd() on some scrypt coins #151
Comments
Sorry, here is the error that is thrown.
|
This probably means that Can you post all your changes somewhere so I can try to replicate? |
Sure. I made detailed post here. https://bitcointalk.org/index.php?topic=214512.new#new That details the network.py values I used as well as the functions I altered to ignore_trailing. That's really the only changes I made. I can't remember if I used your source or the rav3n source https://github.com/Rav3nPL/p2pool-rav but I don't think there are very many differences except the network.py values. If you want, I can zip and and post the p2pool folder i'm running and testing with on my vm. Would that be helpful? |
Any idea where the tx type definition is in the coins source usually? I'm struggling to find it, but I could troubleshoot that if I knew in the coin source where it was. |
I'm also looking into adding more scrypt coins to p2pool. If anyone else wants to work on this together to expand the number of ALT coins supported by p2pools then feel free to PM me or contact SEOCrow on skype. It will benefit all of us if we can determine whats causing these issues with specific ALT Coins. |
It does appear the the structure of that call has been modified a little bit. It appears that a std::string strTxComment; has been added to it. However I am unsure of how to alter the pack.tx_type to work with this addition. Any help would be appreciated. |
Here are the network.py values I altered. There were not other code changes except for the above mentions ignore_trailing=True that I mentioned.
|
Squiggie, I see you have managed to get the pool up and running after all :-) |
No, i haven't been able to make this work with some alt coins that throw this error. It works with some alt coins but not others. The examples I have above for earthcoin are a good example. |
I'm trying to prepare in advance for a new coin based on eac but am running into the exact same issue. I figure it's because of the transaction comment deal...I spent hours on this yesterday and kept ending up back here at this thread over and over. Tried multiple releases, clean installs, different versions, commenting out lines, and now I'm just getting frustrated. Other coins that have transaction comment like Florin (FLO) never got added into P2Pool so I'm guessing this is a bigger issue than either of us think. What needs to be done is have p2pool recognize that the comment line exists and either do something with it or hardcode it to ignore it outright. Preferably I'd like to use the comment line if possible to say the payout came from which pool. |
I've tried to modify the tx_type format in p2pool/bitcoin/data.py a few different ways and I keep running in to errors. The issue seems to be that sometimes there is a tx comment, and sometimes there isn't, and I have no clue how to handle this. I have plenty of scripting experience, but very little programming experience, and pretty much no python experience. Any pointers on how to handle packing a field that may or may not be there would be GREATLY appreciated. I've tried playing with this "PossiblyNoneType" a few different ways as I'm guessing that's how you handle it, but I'm still getting errors no matter what I do. The most recent error I'm getting when I use ('txcomment', pack.PossiblyNoneType("", pack.VarStrType())) or ('txcomment', pack.PossiblyNoneType(0, pack.IntType(256))) is -
|
I've been trying to implement p2pool for some alt coins and lately I've been getting some error messages on several new alt coins that I'm not able to resolve. I'm fairly confident I've been able to input the proper values for the network.py files, but I just can't figure out what the error is referring to.
I was able to track it down these functions.
If ignore_trailing is set to True, the error goes away. I'm assuming that is because the root of the issue is pos is always 1 character larger then data. I just don't know enough about these functions to know what is going on here. I'm not that versed in python.
I changed these values to True and testing this overnight with a coin and although we were able to find blocks, none of them made it into the block chain and no payouts were made. So I assume changing that is messing with the block somehow.
Any advice would be appreciated in how to alter this and make it work for other alt coins.
The text was updated successfully, but these errors were encountered: