Topic: [ANNOUNCE] paccoin a new SHA256D coin is being introduced - page 77. (Read 136571 times)

Breaking news- Novaexchange will stay open
https://novaexchange.com/news/  
 

They aren't lost but I haven't been able to recover them yet from a few test TX I sent off into the ether. I think the rpc for generating rawtx, signing, and sending is generating bad tx code. I've got a few TX sitting at 0 confirms and the coins aren't available in either wallet because the chain is recording them as sent from the host wallet but never confirmed to the old wallet.

I thought I could make a raw TX and send them back to myself but that hasn't panned out yet.

Need to work on that but it's well past my bedtime...

No coins that are sent are lost when there is a orphan. They are simply copied to another block that is valid.
mined blocks on the other hand may not be accepted by the network as the point of proof of stake is that stake blocks take precendence over mined blocks. Stakeholders have a higher say. That is why Paccoin is not susceptible to a 51% attack like bitcoin is.

Please keep us informed of what you see

I read somewhere they are going to hard fork it from DASH and is there early redemption.

PAC Update

Today the Alpha version of the new website has been released. Be aware: an Alpha version is not the version for release to the public.
It is a test version for the mods. Once everything is ok it will be released. Pictures of the new site can be seen under the "important news" section of the PAC Discord chat channel.

Voting for the new PAC logo is still possible. The 6 finalist logos that were selected by the PAC team can be found here:
https://www.reddit.com/r/paccoin/comments/7qdqpe/pac_logo_competition_finalists/


PAC schedule:
January 16, 19:00 GMT voting for the logo ends
January 19: Q&A Livestream
February 1: release of the white paper. Redemption starts for masternodes
March 1: hard fork. The new PACcoin starts that day for everyone!

The explorer is recording TX that have been wiped, just FYI.

I see all transactions and complete balance in explorer for my wallet (3 transactions). But there aren't two from three transactions in my PC-wallet. I see 1st transaction only in my PC-wallet. Also right now i have 93% net synchronization in my PC-Wallet. What should i do - wait for full sync. and i'll see all transaction in my pc-wallet, or should do rescan procedure?

I am having problem with my wallet since yesterday. It was synchronized but suddenly got out of sync. It has been synchronizing since yesterday, but the number of remaining blocks is increasing. A few hours ago it was 2.623.426 of 2.625.536, and now it is 2.623.426 of 2.626.166. In fact, the number of downloaded blocks is remaining the same. The last received block was generated 1 day ago. Maybe it is related to the problem @breakcrypto noticed.

I posted a pull request:

https://github.com/wmcorless/paccoin/pull/12

You can see the code changes. If it's not accepted in a few hours, I can compile the client and post if people want.

Look at the explorer, it's all over there or any of my previous posts. I documented it all there. Set the blockexplorer ( http://paccoinexplorer.com/ ) to 100 last posts. Look at the block heights. Here's a screenshot I just took off the explorer:

(Block height: 2626477 rolls back to 2626415 -- time reverts and the last 62 blocks 'disappear').

See how the height and time goes backwards, that's someone forking the chain and rolling it back (if it were done with hashing power, that'd be a 51% attack). It's a glitch in the trust logic. You can verify that, as I've explained a few pages back, by opening up your debug.log (if you're on linux use:


That'll output the chain updates. The height should always go up, but it doesn't. When it flips backwards, look at the trust score and the hash value. You'll notice it's a full hash which indicates a PoS block (you can paste the block hash into the explorer to see it on the web if you want), and you'll notice the height went down but the trust value went up -- that's the flaw in SetBestChain.

Posting the fork now, I'll compile it and post links if anyone wants them. If not, to each their own. I'd like PAC to succeed again but not like this.

And from now until March is just letting scammers scam. If that's what people want, have at it. It's not what I want from from the crypto world though.

@Breakcrypto: what can i do, or where should I look to get evidence that you are not spreading FUD?
So far i heard of no problems. And even if there were: the new chain will start very soon.

It looks intentional to me. As soon as I made that post, the frequency increased dramatically. You can see it on the explorer in the last few hours, the PoS blocks are reverting several minutes constantly. The chain goes a few steps forward and then flips back a few moments later -- it's barely budged in the last 2 hours.

I'll give the devs a little bit more than then I'm hard forking it and I'll post the code. Trying to close out work for the day. I have a source tree with the needed changes but I haven't had time to post it to git. I'll fork from the repo so it's easy for everyone to see the changes. I'm also going to bump the protocol version from 60070 to 60080 so it'll disconnect bad clients.

If the new fork takes; I'm going to ban the suspect wallets unless everyone is staunchly opposed. Voice your opinion or I'm just going to stick with my plans. I'm happy to let the previous devs handle this (no idea who they are though and their discord is down) but if not, I'll do it. I can also setup a new coin and reverse merge it if other want. Dash / dagger coins are easy enough to spin up too.

I hate scammers -- they make the crypto market shit. I remember this crap from years ago and had hoped it was gone. But when there's money to be made there'll always be some asshole trying to take if from others.

Thoughts?

P.S. I can only do this part time, but I'm happy to help when I can. I definitely have time to patch this bug  -- since I've already done it, lol.

Please let us know if the devs or exchanges posted any response to your email.  Much appreciated!

If it's not address immediately, I suspect it'll collapse the coin. I mean, it should at least. The chain is in complete disarray -- there's no stability at all.

Can they generate enough to impact the doge market value?  I'm getting worried with my doge investment since PAC>>Doge>>BTC, doge gets the first hit

Exchanges need to stop accepting PAC right now until this is corrected. They're being scammed. Someone is running this scam as quickly as possible -- luckily, it's easy to pull those wallets.

I suggest a hard fork and ban for all of the people who were dumping/double spending. If the devs REALLY want to spawn a new coin, then they need to clean this up, ban any wallets that were involved, and get the trust of the exchanges back. I've emailed all of them.

If there is no action taken shortly, ignore this coin and move along. It's in a bad state right now.

Everyone should go look at the chain right now, it's bouncing around like mad. I've just watch it reset multiple times. If you scan the debug log for SetBestChain you'll see it flipping forward and then back -- go check, don't take my word for it.

I'm not sure if it's intentional or not but if so, you're being scammed. Double spends are completely possible by a trust attack -- just like a 51% attack. In case you were curious, yes, that's the SAME way a 51% works. Run the chain up a certain height, flip it back, erase the TX, run the chain forward, flip it back, etc.

People are playing with the chain I think.

USDT is a awesome idea. I think he is coming out with some news this week...

Read back a few pages, I explain what is happening to your blocks -- the chain is constantly forking due to a bug in the PoS logic and the way the SetBestChain logic is working.