 Show Posts
|
|
Pages: « 1 2 3 [4] 5 »
|
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. |
|
|
|
@adaseb if somebody is going to create block explorer
Ok, i will.  The more you reveal what you are doing the better for us. Keep talking.
Take it easy. You can't stop the coin if it will be good enough. Anyway we all know that the concept of the coin is perfect. Having human-readable accounts. No need to keep blockchain, that can be removed at any time with safety for all balances. Is not it amazing? Yes! I am not against the coin, I am against those types who keep on cheating because the code is bugged. There are honest miners and this coin is not intended for the cheating ones. its for decentralized, honest and fair distribution. If adaseb will permit, we will hardfork this coin, and block those cheating accounts. If i have to do it alone then so be it. Goodluck to you. If your account is flagged as malicious, I am sorry but it will be blocked. There is a lot of controversy that comes with blocking accounts/addresses/transaction or performing blockchain rollbacks. Reason being that crytocurrencies are suppose to be immutable and decentralized. Suppose, I'm not saying I will do this, but suppose we block certain accounts that cheated on Pascal Lite. If we do this, how will the coin have any trust when we can at anytime in the future block some whale who owns a substancial part of the coin from accessing to their account? Nobody will buy PascalLite because one developer has too much control and the coin is very centralized. This is actually the very reason why Ethereum lost a large part of their marketcap during the summer by how they handled the DAO hack situation. And alot of people lost faith in Ethereum simply because one developer has too much control. The only accounts that will cease of operations are those of the cheaters. if we hardfork i dont think there will be much malicious miner then as now. the new code will be improved to prevent these bad actors and im confident that whale acquires his part of the coin fairly through the improved code. Im also looking at assets on top of pascal chain. But coding it on pascal will be a challenge. eventually we'll figure it out. |
|
|
|
@adaseb if somebody is going to create block explorer
Ok, i will. The more you reveal what you are doing the better for us. Keep talking.
Take it easy. You can't stop the coin if it will be good enough. Anyway we all know that the concept of the coin is perfect. Having human-readable accounts. No need to keep blockchain, that can be removed at any time with safety for all balances. Is not it amazing? Yes! I am not against the coin, I am against those types who keep on cheating because the code is bugged. There are honest miners and this coin is not intended for the cheating ones. its for decentralized, honest and fair distribution. If adaseb will permit, we will hardfork this coin, and block those cheating accounts. If i have to do it alone then so be it. Goodluck to you. If your account is flagged as malicious, I am sorry but it will be blocked. |
|
|
|
This is like dancing but the dancers have different tunes. Its fun right xiphon?
Bullshit. Sending transactions will not forbid to you to mine block with previous block timestamp. It is obvious. I don't know how mmcmc coded his pool but it is pretty easy to take timestamp from preious block header, but not from getwork RPC reply from daemon. It is pretty easy and not a problem for network. Nothing to say to you. You misunderstanding how any decentralized system works, essentially cryptocurrencies. It seems to me that you have plans to confuse readers about how the coin is functioning. Or maybe you are failed with starting your own coin and now you are trying to stop PascalLite? All "problems" that you are "flooding" about is totally bullshit. Nothing to explain here. "Cheating" in a such way how you are talking about in your posts is not exists. One problem that coin have right now it - is having very small amount of miners. So a guy with 10 GH/s can mine all blocks and build his own blockchain faster than all other miners can build together. I explained it very clear but you don't understand that. But it is not PascalLite problem. As network will grow this would not be an issue. Anyway, don't know why you want to bring that disinformation here and don't want to know. You are just a troll. The more you reveal what you are doing the better for us. Keep talking. |
|
|
|
|
This is like dancing but the dancers have different tunes. Its fun right xiphon?
|
|
|
|
|
@adaseb if somebody is going to create block explorer, get it only on uncorruptable masternode.
|
|
|
|
known bugs:
1.Timestamp field not checked on realtime
a. solution for now: flood the chain with transaction every 3-4 secs, that way we all have equal chance of finding solution in 3-4secs but actual solution is on 3(c). he cannot time cheat because daemon includes all tx in pow verification.
I have stopped reading at that point. This won't work. I think somebody is already doing this. They keep sending micro amounts to 0-10 account. Seems like its coming from different source addresses. Its 1 way to battling miner "mmcmc" timestamp attack but futile on miner "Beta ?x----------" As you know, other miner cannot solve blocks if previous block time is tampered. Now, this micro amounts tx is *to make* them waste time. |
|
|
|
known bugs:
1.Timestamp field not checked on realtime
a. solution for now: flood the chain with transaction every 3-4 secs, that way we all have equal chance of finding solution in 3-4secs but actual solution is on 3(c). he cannot time cheat because daemon includes all tx in pow verification.
I have stopped reading at that point. This won't work. Yes I saw a case where miner " Beta ?x------ " rejected 4 tx and only include 7 tx of all 11 on queue. gbt already implemented? good job. funny it got accepted network wide. how many nodes you hosted? 30? 50? this coin has no value yet. Is it that easy to hack the daemon? |
|
|
|
they didn't reply my to PM.
Still cant find you message in my inbox. Will try to send one to you. Sorry I got your nickname confused with some other developer. Send me a PM so we can discuss. oh wait adaseb, just want to let you know that i feel 99.99% xiphon is mmcmc. just a feeling, could be wrong.  I don't know if he is mmcmc. I actually got a PM from mmcmc and he said that he is not cheating and that he is finding all the blocks because he has lots of GPUs pointed to this coin. A few weeks ago, I got another PM, it was from either RAY____ or that New Node guy and he also said the exact same thing. That he is not cheating and he has many GPUs pointed at the coin. He sent me photos of his farm with 200 GPUs or so. So I don't know what to believe and that's why I rather not "relaunch" or "ban accounts" since the evidence is non-conclusive. oh old sebastian sebastian! of course they will deny that. but its conclusive enough. Ray is using a pool but setting a few seconds to minutes offset. but mmcmc aka mcmcmc aka lanla is using the time altering ninja technique. Yes they have much GPU's but still cheating. The types of ray and those with pool are rewriting the blocks from the start. Thats is what I am against. I pity Slava_K "OLORIN". he is an honest fellow but cannot find anything because you say code is law. let's amend the law. Ban them. Lock down the accounts. A bank would never release money if there is a court order to freeze the accounts of criminals. Now we release that court order on next wallet. Bye bye many days of cheating!! My advice to you then is to fix the code yourself and then just launch a brand new coin. Since it seems that 90% of the entire blockchain was mined under false pretenses. Because it seems whichever way I go, it will leave alot of hate either way. I "ban" these accounts and they will send me threatening PM like before. I "don't" ban these accounts and the smaller miners will send me threatening PM's. Ok I'll compromise. How about we allow them to do transaction to only 1 account, to account 0-10 for project developments. Surely you will need funds for this chain? They can either send it to that account only and help you or hold on to something they cant touch. how about that? I can grep the blocks and the account they mine. and 1 more thing. I like when you are on front, you are an honest level-headed fellow.  The problem with this approach is that the cheaters won't come forward and admit that they actually cheated and let alone forfeit all their coins for nothing in return. So it would benefit some but not everybody. Yes I tried to be as honest as possible however it probably wasn't a good idea for myself to get involved with this coin with having very little programming knowledge. There are issues with this coin but I can't get them fixed myself, I need to rely on others but nobody has volunteered so far. One developer PM me and said he will try and fix the most critical issues with this coin and we'll see how it will go. If you want to help and get some of these bugs fixed here is the place where you can post instead of this forum https://github.com/adaseb/PascalLite/issues/1Sorry I dont trust github now. Here is the scenario: a. bug 1 can be fix by bug 3. b. bug 2 can be fix by coding the existing getblocktemplate (there are many) c. bug 3 if will be coded, you'll need at least 40 rigs to run a test so you'll need a big miner whos willing to lend his services 1. run scenario at even (18 honest and 18 evil) and see how will the sbh protection will react 2. run 1 big evil (1 miner and 1 evil supernode) with more than 51% hashrate on the network. less 49 percent honest and record how sbh protection react 3. run 2 big evil (2 miner and 2 evil supernode) with at least 66% hashrate and see how sbh protection reacts. 4. run majority evil but smaller hashrate and how see sbh will react. *if in all scenarios, honest masternode is not corrupted then your good to go. c. set a hardfork block number 1. after the hardfork block previous wallet version cannot connect 2. (my banning and lock down proposal) after hardfork block, disallow transactions until let say 250 blocks forward, only block rewards will be accepted. the wallet will take a snapshot of all accounts and track all movement of all cheater accounts and store those banaccounts.db(encrypt it, superencrypt). 3. after 250 blocks tx can now proceed normally. d. after a week or two release a new wallet as hardfork wallet is code heavy. e. smile. For testing purposes we will most likely just launch a testnet version, we won't need 200 GPUs to test. We can also for testing purposes start with a lower diff and you can do the testing with multiple GPUs. That's the big misconception on crypto of not actually stress testing it. many have that number of rigs nowadays. |
|
|
|
they didn't reply my to PM.
Still cant find you message in my inbox. Will try to send one to you. Sorry I got your nickname confused with some other developer. Send me a PM so we can discuss. oh wait adaseb, just want to let you know that i feel 99.99% xiphon is mmcmc. just a feeling, could be wrong. I don't know if he is mmcmc. I actually got a PM from mmcmc and he said that he is not cheating and that he is finding all the blocks because he has lots of GPUs pointed to this coin. A few weeks ago, I got another PM, it was from either RAY____ or that New Node guy and he also said the exact same thing. That he is not cheating and he has many GPUs pointed at the coin. He sent me photos of his farm with 200 GPUs or so. So I don't know what to believe and that's why I rather not "relaunch" or "ban accounts" since the evidence is non-conclusive. oh old sebastian sebastian! of course they will deny that. but its conclusive enough. Ray is using a pool but setting a few seconds to minutes offset. but mmcmc aka mcmcmc aka lanla is using the time altering ninja technique. Yes they have much GPU's but still cheating. The types of ray and those with pool are rewriting the blocks from the start. Thats is what I am against. I pity Slava_K "OLORIN". he is an honest fellow but cannot find anything because you say code is law. let's amend the law. Ban them. Lock down the accounts. A bank would never release money if there is a court order to freeze the accounts of criminals. Now we release that court order on next wallet. Bye bye many days of cheating!! My advice to you then is to fix the code yourself and then just launch a brand new coin. Since it seems that 90% of the entire blockchain was mined under false pretenses. Because it seems whichever way I go, it will leave alot of hate either way. I "ban" these accounts and they will send me threatening PM like before. I "don't" ban these accounts and the smaller miners will send me threatening PM's. Ok I'll compromise. How about we allow them to do transaction to only 1 account, to account 0-10 for project developments. Surely you will need funds for this chain? They can either send it to that account only and help you or hold on to something they cant touch. how about that? I can grep the blocks and the account they mine. and 1 more thing. I like when you are on front, you are an honest level-headed fellow. The problem with this approach is that the cheaters won't come forward and admit that they actually cheated and let alone forfeit all their coins for nothing in return. So it would benefit some but not everybody. Yes I tried to be as honest as possible however it probably wasn't a good idea for myself to get involved with this coin with having very little programming knowledge. There are issues with this coin but I can't get them fixed myself, I need to rely on others but nobody has volunteered so far. One developer PM me and said he will try and fix the most critical issues with this coin and we'll see how it will go. If you want to help and get some of these bugs fixed here is the place where you can post instead of this forum https://github.com/adaseb/PascalLite/issues/1Sorry I dont trust github now. Here is the scenario: a. bug 1 can be fix by bug 3. b. bug 2 can be fix by coding the existing getblocktemplate (there are many) c. bug 3 if will be coded, you'll need at least 40 rigs to run a test so you'll need a big miner whos willing to lend his services 1. run scenario at even (18 honest and 18 evil) and see how will the sbh protection will react 2. run 1 big evil (1 miner and 1 evil supernode) with more than 51% hashrate on the network. less 49 percent honest and record how sbh protection react 3. run 2 big evil (2 miner and 2 evil supernode) with at least 66% hashrate and see how sbh protection reacts. 4. run majority evil but smaller hashrate and how see sbh will react. *if in all scenarios, honest masternode is not corrupted then your good to go. c. set a hardfork block number 1. after the hardfork block previous wallet version cannot connect 2. (my banning and lock down proposal) after hardfork block, disallow transactions until let say 250 blocks forward, only block rewards will be accepted. the wallet will take a snapshot of all accounts and track all movement of all cheater accounts and store those banaccounts.db(encrypt it, superencrypt). 3. after 250 blocks tx can now proceed normally. d. after a week or two release a new wallet as hardfork wallet is code heavy. e. smile. |
|
|
|
they didn't reply my to PM.
Still cant find you message in my inbox. Will try to send one to you. Sorry I got your nickname confused with some other developer. Send me a PM so we can discuss. oh wait adaseb, just want to let you know that i feel 99.99% xiphon is mmcmc. just a feeling, could be wrong. I don't know if he is mmcmc. I actually got a PM from mmcmc and he said that he is not cheating and that he is finding all the blocks because he has lots of GPUs pointed to this coin. A few weeks ago, I got another PM, it was from either RAY____ or that New Node guy and he also said the exact same thing. That he is not cheating and he has many GPUs pointed at the coin. He sent me photos of his farm with 200 GPUs or so. So I don't know what to believe and that's why I rather not "relaunch" or "ban accounts" since the evidence is non-conclusive. oh old sebastian sebastian! of course they will deny that. but its conclusive enough. Ray is using a pool but setting a few seconds to minutes offset. but mmcmc aka mcmcmc aka lanla is using the time altering ninja technique. Yes they have much GPU's but still cheating. The types of ray and those with pool are rewriting the blocks from the start. Thats is what I am against. I pity Slava_K "OLORIN". he is an honest fellow but cannot find anything because you say code is law. let's amend the law. Ban them. Lock down the accounts. A bank would never release money if there is a court order to freeze the accounts of criminals. Now we release that court order on next wallet. Bye bye many days of cheating!! My advice to you then is to fix the code yourself and then just launch a brand new coin. Since it seems that 90% of the entire blockchain was mined under false pretenses. Because it seems whichever way I go, it will leave alot of hate either way. I "ban" these accounts and they will send me threatening PM like before. I "don't" ban these accounts and the smaller miners will send me threatening PM's. Ok I'll compromise. How about we allow them to do transaction to only 1 account, to account 0-10 for project developments. Surely you will need funds for this chain? They can either send it to that account only and help you or hold on to something they cant touch. how about that? I can grep the blocks and the account they mine. and 1 more thing. I like when you are on front, you are an honest level-headed fellow. |
|
|
|
they didn't reply my to PM.
Still cant find you message in my inbox. Will try to send one to you. Sorry I got your nickname confused with some other developer. Send me a PM so we can discuss. oh wait adaseb, just want to let you know that i feel 99.99% xiphon is mmcmc. just a feeling, could be wrong. I don't know if he is mmcmc. I actually got a PM from mmcmc and he said that he is not cheating and that he is finding all the blocks because he has lots of GPUs pointed to this coin. A few weeks ago, I got another PM, it was from either RAY____ or that New Node guy and he also said the exact same thing. That he is not cheating and he has many GPUs pointed at the coin. He sent me photos of his farm with 200 GPUs or so. So I don't know what to believe and that's why I rather not "relaunch" or "ban accounts" since the evidence is non-conclusive. oh old sebastian sebastian! of course they will deny that. but its conclusive enough. Ray is using a pool but setting a few seconds to minutes offset. but mmcmc aka mcmcmc aka lanla is using the time altering ninja technique. Yes they have much GPU's but still cheating. The types of ray and those with pool are rewriting the blocks from the start. Thats is what I am against. I pity Slava_K "OLORIN". he is an honest fellow but cannot find anything because you say code is law. let's amend the law. Ban them. Lock down the accounts. A bank would never release money if there is a court order to freeze the accounts of criminals. Now we release that court order on next wallet. Bye bye many days of cheating!! EDIT: the time altering ninja technique finally revealed by our great "xiphon the revelear" on https://github.com/adaseb/PascalLite/issues/2 |
|
|
|
they didn't reply my to PM.
Still cant find you message in my inbox. Will try to send one to you. Sorry I got your nickname confused with some other developer. Send me a PM so we can discuss. oh wait adaseb, just want to let you know that i feel 99.99% xiphon is mmcmc. just a feeling, could be wrong. |
|
|
|
Having more pools will make network more healthier.
Look at other currencies, we need to have at least 3..5 pools.
More pools ? Is there a pool already ?  can you add a pool for this? it's not different than adding it for classic variant Absolutely not - there's enough trouble with the other variant. I'm glad when I can shutdown the other pool @Amp We'll fix it first before we ask ocminer to reconsider. This blockchain is garbage. Who will fix the coding? I already said before I don't have the programming experience to fix all those issues. Also if you fix the code you are making it mandatory to ban certain accounts under your terms, I don't agree to this. Think "code is law" like it was with ETH-DAO hack. Code is law is good when the code works, but not when it's just a "big bug" and nothing else  ocminer dont laugh at us you big dog. |
|
|
|
Having more pools will make network more healthier.
Look at other currencies, we need to have at least 3..5 pools.
More pools ? Is there a pool already ? can you add a pool for this? it's not different than adding it for classic variant Absolutely not - there's enough trouble with the other variant. I'm glad when I can shutdown the other pool @Amp We'll fix it first before we ask ocminer to reconsider. This blockchain is garbage. |
|
|
|
|
known bugs:
1.Timestamp field not checked on realtime
a. solution for now: flood the chain with transaction every 3-4 secs, that way we all have equal chance of finding solution in 3-4secs but actual solution is on 3(c). he cannot time cheat because daemon includes all tx in pow verification.
2.transaction bug -daemon issue new work to miner causing hashing start again from scratch. unlike on getblocktemplate where it works only on what was previously accepted by the mempool.
b. solution getblocktemplate on walletupgrade -hard to do but mmcmc can do it.
3. time-roll but sbh accepting it. sbh is supposedly the checkpoint.
c. solution add node consensus on time. nodes will be dependent on peers for timestamp. add node calls and get nodecallreply.timestamp and issue checking sequences on this. once nodes consensus is made on block broadcasted to network, sbh lockdown until another consensus of nodes on the new block. no more rewriting. also will result to proper block spacing dependent on established frequency of nodecalls.
a. effects: so many fork-off. miners with high hashrate but cheating will fork off as sbh cannot be rewritten. honest nodes will check cheaters block submission but will deny it ofcourse, if cheater has his own hosted supernode, then his wallet and his supernode will fork off as long as masternode and honest node remain uncorrupted. (my thought:so what fuck them off cheaters)
also, penalize the cheaters, on wallet upgrade hard code lock down on cheaters account. bye bye cheater. many days on cheating wasted.
4. super super stupid difficulty retargeting. -adaseb is also gaming this bug.
a. solution- copy others. only those succesful coins. (copy/paste)
more bugs to update:
|
|
|
|
Having more pools will make network more healthier.
Look at other currencies, we need to have at least 3..5 pools.
More pools ? Is there a pool already ? coincidence or not but it is exactly how nanopool works the way mmcmc attack this chain. mmcmc has a pool but having a hard time cheating when there is a transaction so he retreat back to the modified daemon he is using now. If adaseb would only listen that timestamp is going to be dependent on other nodes and would lock this cheaters account, we could make lite better than orig. I can only admire how good a coder mmcmc is but sad that he is using it the wrong way. Enough man your sack is full! |
|
|
|
any good and stable pool for zcash expect fly pool
yes looks like flypool is back at stealing shares. The miner shows a constant 973-980 but at flypool it only shows between 850-963. Time to move out Maybe it's not stealing... Maybe it's Claymore's fee + flypool fee? not talking about rewards, talking about hashrates. I even give you 2.5% for fee staled and invalid. The expected average would be 948. My average is 884. What a difference considering my average before was ~940 I get 1815 reported from my PC. I average 1745 in flypool. Thats 4% less. Yeah I get the same about 5-6% is lost somewhere Whenever I'm pool mining, I automatically deduct 5%. You simply don't mine on a pool, where you have to traverse the 'Net to get work and submit results, and expect to get the same outcome as mining solo directly against a local node. yeah right david. stop your hypocrisy |
|
|
|
adaseb:
Enable "issues" feature on github repository (done via "repository settings").
To all:
Guys, instead of spamming blockchain, please, create issues on github. It is more appropriate place where we all can discuss technical details, features and fixes.
This forum is a way uncomfortable to talk about code.
xiphonCan you explain how to reproduce the bug on your issue report on github, seems orig pascal dev is blind. We can make pascal lite better. Your stash is enough i think. Its now time to fix this bug. |
|
|
|
Before we start the crowdfunding for the Crytopia listing, I want to get the code fixed first. Because even though nobody time cheats anymore people are still constantly mad and somebody is flooding the Payload messages during transactions with hate and threats.
Sometime this week when I have some free time i'll update our wallet to the latest 1.5.1 version.
After that I will get in touch will Albert and come up with a solution to get the time-drift issue fixed once and for all.
... sorry Dude - you are just a copy-cat and no coder - but who ever likes this kind of coin ^^ Shhh. STFU if you have nothing good to say. Some of us may help on this. I just hate when there is visible timestamp altering but adaseb is denying it. run a miner and compare the timestamp of the nonces you find and compare it to the timestamp of the published blocks. observe. I looked at the code you posted above, however how do I call the nodes every 5000ms to get the nodecall.timestamp. I enabled the "issues" on my Github. https://github.com/adaseb/PascalLiteIf you guys help me fix the code I can have the new wallet published faster. I want to propose a lockdown on cheaters account number like how a bank does. we'll close and he cant touch it forever after the release of the new wallet. Also, update must be mandatory as previous wallet will be denied connections. If you agree. Also, are you looking at the timestamp altering techniques of these ninjas? We can't lock down certain accounts and we can't relaunch. Its too harsh and this coin was out for already a month and there are almost half a million coins out there. It won't be fair for the miners who put in their hash power and electricity for this coin. We need to fix the bug and just continue on from there. No relaunch. Same old but just a few adjustment. Its like were going on a hardfork to prevent timestamp and bugs improvement like the original pascal. where everything will be cross reference to the code of the new wallet. The cheaters account be on invalid operations from release forward. If you are honest then no problem, if not then you have to pass the guards at the gate. |
|
|
|
|
