-
Notifications
You must be signed in to change notification settings - Fork 66
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
[MOON] RPC-connection #105
Comments
RPC command "help" is no longer throwing back required string. |
try 9a00696 |
Just cloned again freshly. Then starting p2pool it gives me: |
I`ll check it later, probably missing comma or smth.
2017-12-18 17:02 GMT+01:00 coinflow <notifications@github.com>:
… Just cloned again freshly. Then starting p2pool it gives me:
...
yield helper.check_genesis_block(bitcoind, 'bd687cbbac4842724d4b1dfd2e1a6c
e35d765db05635b3ebd3810ba66ac5aee9')))
^
SyntaxError: invalid syntax
...
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#105 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABCxi_sJez_1LehiL_czQ16f-Cx8GhHEks5tBoyGgaJpZM4RFivP>
.
|
This seems to work: RPC_CHECK = defer.inlineCallbacks(lambda bitcoind: defer.returnValue( So the problem was obviously in number and position of the brackets. Could you consolidate the networks-files for Mooncoin? So it would be great to have this consolidated based on mooncoin.py, I assume? |
Changed brackets c78d7f2 |
But not one with capital M and one with small m, right? |
Done. |
Great! Thanks. |
I tried using the new mooncoin.py and recomplied but I am getting crazy DOA shares, and my miner is showing that I found 70,000 Blocks, and then my time to block is showing 14038880326535135797651516507108282486575107470786560.0 years |
still not working, and I have a lot of people that would like to use or create Mooncoin Nodes. Can we do some testing? |
Hi gblass, do you mean the miner found 70000 blocks, or shares? A very high rate of DOA-shares at the beginning is normal. That should level out over time. At least here it is. Have you opened the relevant ports (see the code), so that your node can connect with others and get in sync? The time to block is indeed strange, but I assumed, that is normal, if the sharechain is new/reset and the first block not found already ...?? Rav3nPL? What are your thoughts? Could you set up a test node and connect to the Mooncoin P2Pool, in order to check whether everything runs correctly? |
Maybe the same problem like here: #106 ? |
I'll try to run mooncoin node (core and p2pool) today.
Will see.
27.12.2017 9:36 AM "coinflow" <notifications@github.com> napisał(a):
… Maybe the same problem like here: #106
<#106> ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#105 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABCxiyjgYjA7I0SmOpXHenDNQ6bBEZFPks5tEgGNgaJpZM4RFivP>
.
|
@Rav3nPL Hi, I'm Vassilis the new official mooncoin dev. if you need any help I'm here! My email also is mooncoincore@gmail.com! |
if you are with just a software miner everything is fine.. if you connect with antminer(support Scrypt) for example (500MH/s) in few secs.. in miner status page you got few thousands "Found Blocks". |
Just updated repo, It is working on my side, connected to 3 P2Pool peers, reorganized sharechain. |
|
Miner is probably interpreting accepted shares as blocks found. |
its antminer L3+ 505MH/s |
Pool log:
Block ETA is odd, need look into current P2Pool LTC code, maybe I`m missing something. |
Well, I`m not 100% sure but this code is basing on older P2Pool, it is not prepared for SegWit and it can produce invalid blocks... |
How can we see, whether we found an invalid block? |
Not with the new wallet yet. With the older ones we found a lot of blocks. The last block was this one: https://chainz.cryptoid.info/moon/block.dws?1151546.htm |
I can confirm with @coinflow we used to get blocks often, nothing since use of the new wallet. |
If no one mine coin I can't resolve anything. |
Do you want me to reconnect? I dont mind, but I have ran this one on my own node for almost 24 hours and no change.
Please let me know
…Sent from my iPhone
On Dec 28, 2017, at 11:08 AM, Rav3nPL ***@***.***> wrote:
If no one mine coin I can't resolve anything.
My node will be up few more days.
If no one use this P2Pool I'll kill it.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
https://bitcointalk.org/index.php?topic=1733963.msg27112792#msg27112792 |
i have pointed ny antminer to your pool again. |
Hi Rav3n, |
If retarget is broken wallet should not sync nor accept blocks from "good"
nodes.
RU sure it is a issue?
30.12.2017 4:57 PM "MoonCoinCore" <notifications@github.com> napisał(a):
… @Rav3nPL <https://github.com/rav3npl> @coinflow
<https://github.com/coinflow> @gblass <https://github.com/gblass> I found
the problem.. is in the wallet code retarget function. I'm trying to fix it
now..
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#105 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABCxiwA_NBfEG8O0RQF2Dj2bJHxhLyRDks5tFl13gaJpZM4RFivP>
.
|
Anyway, valid block is found.
Pool seems working, but this block ETA is odd...
http://moonchain.net/block/66440e947b60a4b2da028cb087c1e35c520612ef185f21deab6a4a9ebdb60687
30.12.2017 4:57 PM "MoonCoinCore" <notifications@github.com> napisał(a):
… @Rav3nPL <https://github.com/rav3npl> @coinflow
<https://github.com/coinflow> @gblass <https://github.com/gblass> I found
the problem.. is in the wallet code retarget function. I'm trying to fix it
now..
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#105 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABCxiwA_NBfEG8O0RQF2Dj2bJHxhLyRDks5tFl13gaJpZM4RFivP>
.
|
I have gave the code for test.. if you want to test it the "fixed" code is in https://github.com/mooncoincore/wallet . |
@Rav3nPL please give me your btc address to send you a small donation for your help! |
Thank you @coinflow @Rav3nPL @mooncoincore |
@mooncoincore fix in wallet also fixed block ETA display in pool. For segwit support I need move all my patches to new codebase, because current is bit obsoloete (like 2 versions behind). It is still working fine for non-segwit coins. |
It is regulated in another way. |
Basically right, that Mooncoin is not really mineable with CPU and GPU. But you can use cgminer/minerd with ASICs, too. |
And what gblass is asking is, what could be a nice upgrade for P2Pool-technology, if not already available: the software could adjust the mining-difficulty according to the hashrate of the single miner. Just like it is in the MPOS- and NOMP-pools. Could this be developed? Would be great. |
Seems that p2pool LTC has around 18,000 share for the 3day sharechain. With mooncoin, seems to be only around 3000 shares? So once p2pool Moon reached 50GH, many miners had trouble submitting shares that didnt get pushed out of the sharechain within hours. The miners are all using ASICs... |
We can change share chain data, but it require "restart" of the sharechain. Lenght of share chain not changing share diff, share chain need to be longer than pool block ETA.
OFC it also need chain reset. |
Hi Rav3nPL,
could I ask you to help Mooncoin again with tuning p2pool-rav according to the new wallet/client? That would be great.
The new wallet ( --> https://github.com/mooncoincore/wallet ) was compiled and installed alongside a freshly cloned p2pool-rav. But obviously an RPC-call is not possible.
I have found this one: litecoin-project/litecoin#371 where the user also has problems with the latest Litecoin-wallet to make it possible to work together with a p2pool-code. Since the newest Mooncoin-wallet is based on the latest Litecoin (as far as I know), could it be, that the linked solution would work in your p2pool-version for Mooncoin, too? See here: https://github.com/ilsawa/p2pool-ltc/commit/2af67a8cc7d0c498479f080f0652e02c4c826497
Since I don't know what the correct value for the Mooncoin-genesis-block would be, could you test that and possibly change the relevant passages in your pool-script to be correct? That would be really nice.
Notice: The new dev has changed back to the "official" naming conventions, meaning, that the paths that the Mooncoin-wallet creates, are with small letters again. Maybe this is of help for your updates of the code.
Thank you very much.
The text was updated successfully, but these errors were encountered: