 Show Posts
|
|
Pages: « 1 2 [3] 4 5 »
|
Folks, i want to intoduce PascalLite pool to you. Pool can be found here: https://pasl.fairpool.xyzUsers who don't have PascalLite account, you can receive one from pool. More details available pool website. Others can mine directly on their accounts. Please notice that PascalLite have 100 blocks maturation height That's why we need to wait until block will be confirmed. Feel free to PM me about any problems that you have met with the pool. So, you are welcome! Thanks for the public pool.Though I see that the current problem will only be elevated by this a couple of magnitude higher. You will see. I implemented time settings as fair as it possible. So no cheating from the pool. Even if you will see that - please, send me a message and i will inspect what happened. This looks a little bit better than the orig pascal but im still seeing negative numers from wetpussy and new node, your pool is showing blocks few seconds behind my system and dedmaroz is still fixing timestamp. Well that's what crypto is. Just hoping it would be a little more tighter. You using the newest version released an hour ago? You can have a timestamp that's in the past but not in the future. We tested this out already, if your timestamp is +15 sec higher than node averages then the block won't be accepted. Yes latest version. This can do for now. Thanks for your hardwork. |
|
|
|
Folks, i want to intoduce PascalLite pool to you. Pool can be found here: https://pasl.fairpool.xyzUsers who don't have PascalLite account, you can receive one from pool. More details available pool website. Others can mine directly on their accounts. Please notice that PascalLite have 100 blocks maturation height That's why we need to wait until block will be confirmed. Feel free to PM me about any problems that you have met with the pool. So, you are welcome! Thanks for the public pool.Though I see that the current problem will only be elevated by this a couple of magnitude higher. You will see. I implemented time settings as fair as it possible. So no cheating from the pool. Even if you will see that - please, send me a message and i will inspect what happened. This looks a little bit better than the orig pascal but im still seeing negative numers from wetpussy and new node, your pool is showing blocks few seconds behind my system and dedmaroz is still fixing timestamp. Well that's what crypto is. Just hoping it would be a little more tighter. |
|
|
|
Block explorer is the last piece missing.  Congrats guys. Good work! @adaseb
@xiphon |
|
|
|
Folks, i want to intoduce PascalLite pool to you. Pool can be found here: https://pasl.fairpool.xyzUsers who don't have PascalLite account, you can receive one from pool. More details available pool website. Others can mine directly on their accounts. Please notice that PascalLite have 100 blocks maturation height That's why we need to wait until block will be confirmed. Feel free to PM me about any problems that you have met with the pool. So, you are welcome! Thanks for the public pool.Though I see that the current problem will only be elevated by this a couple of magnitude higher. |
|
|
|
How i can get wallet and adr?
I'll give you an account number for free. Send me your public key Better. Pascal Lite is a good crypto community. |
|
|
|
How i can get wallet and adr?
You have to mine to have an account or you can buy it from someone. The address here is referred to as account, a very easy to remember number system unlike bitcoins addresses. Download the wallet from the first post of the OP, let the wallet sync to the current block(10500) then you can start to mine. When you win a block you will be given 5 accounts and first account in that contains the block reward of 50 pascal lite coins. You cannot receive from other user any coins if you do not have any account. good luck. Welcome to Pascal Lite. |
|
|
|
Yeah it seems to be the same at me too. ~90% cpu load and only 1600mh/s insted of the 2200mh/s
sgminer accepts commands, for more try help. usually this will do sgminer.exe -k pascal -o stratum+tcp://127.0.0.1:4009 -u x -p x -I 21 -w 64 -g2
|
|
|
|
What's the syntax ? doesn't work for me at the moment  Can`t run for solo. And bat, and with modded configuration file. P.S. " Payload prefix from daemon is of an unexpected size." I'm getting the same and it's not mining... [09:32:08] Payload prefix from daemon is of an unexpected size.
[09:32:08] Initialising kernel pascal.cl with nfactor 10, n 1024
[09:32:09] Initialising kernel pascal.cl with nfactor 10, n 1024
[09:32:09] Initialising kernel pascal.cl with nfactor 10, n 1024
[09:32:19] Waiting for work to be available from pools.
[09:32:52] Payload prefix from daemon is of an unexpected size.
(5s):0.000 (avg):0.000h/s | A:0 R:0 HW:0 WU:0.000/m Yeah I just tried it and got the same thing. I also got the same issue with PascalCoin 1.5.0 Maybe we need to set a special node name and such. Maybe you guys can ask Wolf0 for some info on how to run it. @xiphon
@adaseb
Dont want to put an issue on github myself, but if you want, please do.
Tx bug - miner work repeating from start
Every time a transaction is published on the network, daemon issue new work to miner to include latest tx, as result miner start again from the beginning work. If tx would be as many as possible per block can handle, this would lead to network lag and crawl as pow submitted by miner will be invalid if not all tx is included.
Work around
a. possible integration of existing getblocktemplate into pascal lite.
b. set max tx inclusion per work(1block). Bitcoin does have size limit. (ugly but can do)
Note: documentation only.
The work is restarted from scratch but since the hashing is completely random it shouldn't be an issue. Since each hash is independant of the prior. Is this what you are asking or did I read it incorrectly? shouldn't be problem now. but it makes miner current work to start again that includes the last tx received. if you press the miner to submit work without the last tx, work is invalid. |
|
|
|
Can somebody please explain what's the difference between H/s and Sol/s that nheqminer shows?
1 Sol/s = 2 H/s. Bummer that you give a supposedly definitive answer, and it's exactly WRONG: 1 hash/sec yields ~2 Sols/sec (actually, 1.88 if the miner is implemented well). All the pools, blockchain explorers, etc. are reporting Sols/sec. ______________ Bummer. 1.88 is a theoretical number that the miner will approach for a long period but not true. ______________ Dave oh Dave.  |
|
|
|
|
@xiphon
@adaseb
Dont want to put an issue on github myself, but if you want, please do.
Tx bug - miner work repeating from start
Every time a transaction is published on the network, daemon issue new work to miner to include latest tx, as result miner start again from the beginning work. If tx would be as many as possible per block can handle, this would lead to network lag and crawl as pow submitted by miner will be invalid if not all tx is included.
Work around
a. possible integration of existing getblocktemplate into pascal lite.
b. set max tx inclusion per work(1block). Bitcoin does have size limit. (ugly but can do)
Note: documentation only.
|
|
|
|
Alright everybody calm down... Lately there is too much drama in this thread.
We are trying to fix all these issues. If you want to help then go to the github and review the changes.
We are running a testnet version right now seeing if the attacks are under control.
Really good. whos the dev? saves me a lot of headache. but please do impose counter check on time with other nodes. @xiphonDidn't realize it was you. good luck man. |
|
|
|
Im CMCMC miner, im not cheater, im using my own mining software and its bug with timestamp.
I read timestamp from last block, but not incremented, it is only bug not cheating, i fix this bug this weekend, i dont have time now...
I have a lot of hashingpower, around 8GH/s it is 70-80% pascalhasrate
I helping this coin and i pay electric bill for this.
I repeat: Im not a cheater!
All as what im saying before. You need no to apologize, it is not a bug at all. Having the same timestamp would not help you to mine faster than others. It is just fantasies of our coin-mate code_honesty. And another one time again: FORGING BLOCK WITH THE SAME TIMESTAMP AS PREVIOUS BLOCK TIMESTAMP WOULD NOT HELP YOU TO MINE FASTER. Anyone, please, STOP talking that "having the same timestamps is cheating". It is not. Or prove here and now that this is some kind of cheating. Really? get a life matey. If really wanna help us in this endeavor, post solution, not take advantage of this flaws. People like you nowadays with convoluted mind are thinking breaking protocol is normal, honest and regular and people should just live with it and accept it. Life wont get better if you we are to follow your lead.  |
|
|
|
Well Alpha is definitely cheating. Noticed this for a few of his blocks. Sometimes its 90 seconds ahead. It doesn't help how we point out these bugs in public and then others read about them and exploit them.  This is a daemon problem, the daemon should not accept anything with tampered time and if miner daemon is tampered, network should not accept it. Really needs to be fixed. Can you talk to albert about this? I think he is not aware that we are ahead on bug discovery. |
|
|
|
anyway i fix bug in my mining software soon as posible
and i offering 10.000 pascalLite coins for development.
Thank you very much adaseb will get in touch with you. |
|
|
|
I can donate some pascalLite coins for development Good. that is much needed help. Thank you. To all those miner we labeled cheater follow dedmaroz lead. We might come to an agreement. Ray_____ New Node 2017/2/2 Beta x?---- I have my list. Do it voluntarily. Please. |
|
|
|
Im CMCMC miner, im not cheater, im using my own mining software and its bug with timestamp.
I read timestamp from last block, but not incremented, it is only bug not cheating, i fix this bug this weekend, i dont have time now...
I have a lot of hashingpower, around 8GH/s it is 70-80% pascalhasrate
I helping this coin and i pay electric bill for this.
I repeat: Im not a cheater!
Im listening: You're still not off the hook. On my list you are the number 1. Now explain. wait a few days to fix the errors in my mining software and you see the correct timestamp @demaroz That is not the explanation i expect from you. How do you inject wrong time that is accepted by the daemon and blockchain? I know how its done but i want you to explain this bug. pascalwallet send me this: {"method":"miner-notify","params":[{"block":9816,"version":1,"part1":"58260000CA0220001D17CCB36C9013D8C1EADAD8464912A55142E5E54B1682717A022B7CC198BCA 72000F479055B7199CB14F96401FD68006978B4110B9D5D5653C078DF12931241F2CC20A1070000 000000010001004C6F922A","payload_start":"6D6D636D63","part3":"DFF30B788D9086AB994A81D6641EA3C7295908CFB555006FC25B0EF1BEBFEFDCE3B0C44298FC1C1 49AFBF4C8996FB92427AE41E4649B934CA495991B7852B85500000000","target":714239820,"target_pow":"00000000002DB216600000000000000000000000000000000000000000000000","timestamp":1488361931}],"id":null} i have static timestamp (not incremented, this is bug) "timestamp":1488361931 and i changing only payload and nonce, if i found block, i send input data back to pascalwallet and i get BLOCK, thats all. No cheating, you are crazy man OMG! Ok. Thank you very much for your cooperation. Im inclined to let you off that list. Be cooperative with us and answer our questions sometime later. Adaseb will get in touch with you. Btw, how good are you at pascal programming? in software are amateur, pascal is too compicated for me, my job is low level hardware programming I see. Thanks. Adaseb and I are actually looking for 1 programmer that is good in pascal. Hope someone volunteers. |
|
|
|
|
Any one here in touch with a crypto news? writer blogger of any sort? This is the very same thing that is happening on the main pascal coin.
lets start tweeting.
|
|
|
|
Im CMCMC miner, im not cheater, im using my own mining software and its bug with timestamp.
I read timestamp from last block, but not incremented, it is only bug not cheating, i fix this bug this weekend, i dont have time now...
I have a lot of hashingpower, around 8GH/s it is 70-80% pascalhasrate
I helping this coin and i pay electric bill for this.
I repeat: Im not a cheater!
Im listening: You're still not off the hook. On my list you are the number 1. Now explain. wait a few days to fix the errors in my mining software and you see the correct timestamp @demaroz That is not the explanation i expect from you. How do you inject wrong time that is accepted by the daemon and blockchain? I know how its done but i want you to explain this bug. pascalwallet send me this: {"method":"miner-notify","params":[{"block":9816,"version":1,"part1":"58260000CA0220001D17CCB36C9013D8C1EADAD8464912A55142E5E54B1682717A022B7CC198BCA 72000F479055B7199CB14F96401FD68006978B4110B9D5D5653C078DF12931241F2CC20A1070000 000000010001004C6F922A","payload_start":"6D6D636D63","part3":"DFF30B788D9086AB994A81D6641EA3C7295908CFB555006FC25B0EF1BEBFEFDCE3B0C44298FC1C1 49AFBF4C8996FB92427AE41E4649B934CA495991B7852B85500000000","target":714239820,"target_pow":"00000000002DB216600000000000000000000000000000000000000000000000","timestamp":1488361931}],"id":null} i have static timestamp (not incremented, this is bug) "timestamp":1488361931 and i changing only payload and nonce, if i found block, i send input data back to pascalwallet and i get BLOCK, thats all. No cheating, you are crazy man OMG! Ok. Thank you very much for your cooperation. Im inclined to let you off that list. Be cooperative with us and answer our questions sometime later. Adaseb will get in touch with you. Btw, how good are you at pascal programming? |
|
|
|
Im CMCMC miner, im not cheater, im using my own mining software and its bug with timestamp.
I read timestamp from last block, but not incremented, it is only bug not cheating, i fix this bug this weekend, i dont have time now...
I have a lot of hashingpower, around 8GH/s it is 70-80% pascalhasrate
I helping this coin and i pay electric bill for this.
I repeat: Im not a cheater!
Im listening: You're still not off the hook. On my list you are the number 1. Now explain. wait a few days to fix the errors in my mining software and you see the correct timestamp @demaroz That is not the explanation i expect from you. How do you inject wrong time that is accepted by the daemon and blockchain? I know how its done but i want you to explain this bug. That's very easy, the daemon accepts any time later than last blocks timestamp and not later than +380 sek or so... So you can just send blocks with the same timestamp as the last Block +1 second for example and lower yourself the diff for the next Block a lot (or raise) @ocminer care to explain what you mean by lowering for yourself the difficulty for the next block and raising it for the other miner? this is newsworthy. prepare to be quoted btw. |
|
|
|
Im CMCMC miner, im not cheater, im using my own mining software and its bug with timestamp.
I read timestamp from last block, but not incremented, it is only bug not cheating, i fix this bug this weekend, i dont have time now...
I have a lot of hashingpower, around 8GH/s it is 70-80% pascalhasrate
I helping this coin and i pay electric bill for this.
I repeat: Im not a cheater!
Im listening: You're still not off the hook. On my list you are the number 1. Now explain. wait a few days to fix the errors in my mining software and you see the correct timestamp @demaroz That is not the explanation i expect from you. How do you inject wrong time that is accepted by the daemon and blockchain? I know how its done but i want you to explain this bug. |
|
|
|
|
