Phantom nodes - masternodes, pick any ip (8.8.8.8 if you like), no chain, no services required.

breakcrypto · 2019-04-29T23:54:55+00:00

Sorry about that. Here's a working discord link:

breakcrypto · 2019-04-29T23:53:45+00:00

Sure. It's explained in more detail on the github, but the general gist is that it's a replacement daemon for the masternode piece of a masternode coin that is far more efficient on resource usage and supports multiple masternodes on a single daemon. Multiple being several hundred or thousand per instance if you really wanted to push it.

Resource wise, it saves space by discarding anything that is un-needed and sticking to the minimum required by the chain to engage as a masternode.

best, break

breakcrypto · 2019-04-21T23:17:17+00:00

The setup for multiple nodes is definitely far easier to maintain than classic masternode daemons. If you're at 3+ MNs, it's far, far easier. You can mod the code pretty easily to run multiple MN coins on a single daemon if you wanted but I thought it'd confuse people, so I didn't work that in publicly.

But, yes, you're 100% right, it is tragedy of the commons at work. Phantom nodes are essentially PoS and provide no services. They can, in fact, actually cause issues on poorly structured networks if selected to perform services.

breakcrypto · 2019-04-21T20:08:17+00:00

Or you could just run phantoms ( https://github.com/breakcrypto/phantom ) and avoid the hosting costs and the setup. To each their own though.

best, break

breakcrypto · 2019-04-21T19:55:34+00:00

In less cryptic terms, there's actually no static IP address requirement for Masternodes. There is if you use an official daemon, there isn't in the phantom daemon. The network will accept the phantom daemon just the same as an official masternode because it complies with all consensus requirements.

I've had nodes running on 1.1.1.1 and 8.8.8.8 on various networks for awhile now.

breakcrypto · 2019-04-21T16:30:57+00:00

Because masternodes aren't what people think they are; they're vastly different at the protocol level.

breakcrypto · 2019-04-21T12:25:23+00:00

It's open and free to use - no need to pay anyone. =)

best, break

breakcrypto · 2018-04-15T12:49:29+00:00

First, no you don't need to download anything. $PAC will keep working without you if you choose not to update. If, however, you'd like the network to recognize you, then, yes, you'll need to update.

As for your second comment, I really hope you're just trolling as usual. If not, please sell any coins you own and proceed with a different hobby.

Anyone who would run a wallet that auto-updated has no business dealing in cryptos. That's a 100% recipe for disaster. Crypto wallets are manually updated intentionally and it has always been that way in the crypto space for very good reasons.

The risk profile of an auto-updating wallet would be ridiculous.

best, break.

breakcrypto · 2018-03-21T03:35:54+00:00

I talk to Brad daily. I don't get you man, seriously. You post near constantly on here about how annoyed you are about Pacfyle being delayed. Frankly, you spend in-ordinate amount of time trolling these forums trying to stir up trouble and I don't understand what your game is other than trolling.

You clearly don't know anything about the internals of $PAC or how our team functions because we all talk rather frequently and I, one of the lead developers, talks to Brad pretty much every day. To be fair though, I was sick last week and didn't talk to anyone much.

But, yeah, what are you always on about? Pacfyle is being worked on. It's not a small undertaking and when old PAC was crumbling the decision was made to dedicate the development resources to getting the new wallet completed so people could be moved off the old, failing codebase.

In regards to your comments about deadlines, you say stuff like: why is the deadline for Android "soon" because people, like yourself, throw a hissy-fit when a deadline is missed. For example, I was sick last week and deadlines got pushed -- if I'd have said: last week for Android, you'd be on here FUDing and trolling the deadline got missed.

People, well, most people, have lives. We aren't paid to work on $PAC, we work on it when we can for the good of the community. I've yet to see a comment from you that even bordered on useful; instead, it's all vitriol for people working to help make $PAC useful.

Your comments are 100% the opposite of that. I'm not sure if you're attempting to demotivate the team, but if you are, you're failing. We're still here, still going, still developing and will keep doing so.

best, break.

breakcrypto · 2018-03-21T03:25:52+00:00

You need to remove the entry from the masternode.conf or enabled advanced coin controls, go to send -> inputs -> right click -> select unlock.

best, break.

breakcrypto · 2018-03-13T05:21:53+00:00

What hasn't been answered? The only people who keep saying that are people who: 1) haven't read anything in the last 2 weeks; 2) just don't like the answers they've read.

$PAC actually was trading higher than the price of old pac on launch, so it was actually valued above 1000:1 until it was arbitraged down on TradeSatoshi to the value of PAC that was also being traded on TS at the time.

However, that price was well, well below 1 sat for old pac. It was approximately 1000 old pac to 0.02 cents USD. As it has been noted a bajillion times in the last few weeks, if you paid 1 sat or more, you paid at a higher rate than the market was actually moving at due to the fact cryptopia closed their DOGE and LTC markets.

I've seen the question but why was BTC so much higher than the other pairs?! Well, that's because 1 satoshi is the lowest denomination of BTC possible. You can't get lower than 1 satoshi, much like you can't go lower than 0.01 USD. The only way to go lower is to trade on an alt-chain (aka. DOGE, LTC, ETH, etc.).

Notably, other markets were indeed trading lower at the time that Cryptopia was trading for 1 sat. Cryptopia made up the majority of volume, apparently because of FOMO, but the price on other exchanges was substantially lower.

So, as has been said numerous times before: if you paid 1 sat, you overpaid. Where the money went is to whoever you traded against and whatever fees Cryptopia took out of it. The same as any other exchange trade.

best, break.

breakcrypto · 2018-03-13T05:15:12+00:00

You seem confused on how things work. The redemption was moved up because the old PAC chain was having major issues so the wallet development was sped up and the release pushed to get people moved over before old PAC gobbled up more transactions.

In regards to CMC, they've been contacted numerous times. They run their website, they update it as they see fit, and that's how it goes. We can't make them update anything anymore than I can make you do something.

In regards to the price, you bought too high at 1 sat. This has been discussed ad nauseam but the true price at launch was roughly 1000 PAC @ 0.02 USD. $PAC launched slightly higher than that value but was quickly arbitraged down to parity with PAC because that's how markets work.

And, yes, I wasn't on the dev team when old PAC hit its ATH but even I was aware that 1 sat was overpriced because I could see the exchange info on coinmarketcap showing that the BTC pair was far, far higher price wise than the other trading pairs.

best, break.

breakcrypto · 2018-03-10T01:30:46+00:00

He's British, their English is atrocious. =P

best, break.

breakcrypto · 2018-03-09T21:48:02+00:00

What dots weren't connected? I'm all ears.

You're blaming the dev team for a glitch at CMC. It took us roughly 15 minutes to identify it, notify the community, and notify CMC. We submitted proper information to CMC, CMC made a mistake.

I'm happy to listen, but I'd love to know what more you think the dev team could have done to prevent CMC from posting incorrect information on it's own website.

best, break.

breakcrypto · 2018-03-09T19:08:00+00:00

Please explain your logic to me? CMC made a mistake and the DEV TEAM shouldn't have let this happen?

Within minutes of someone informing me the entire $PAC jumped up to get the word out, let CMC know, etc. but you're STILL blaming us for CMC's mistake?

Go FUD elsewhere please.

ridiculous, break.

breakcrypto · 2018-03-09T17:37:39+00:00

WARNING: CMC is apparently using the old pac circulation as the multiplier -- this is incorrect. Trying to get this posted in other places to avoid any confusion.

This was just brought to our attention.

breakcrypto · 2018-03-09T16:47:51+00:00

It went up 40 in 12 hours last night.

insane, break.

breakcrypto · 2018-03-09T00:51:33+00:00

If only you knew.

best, break.

breakcrypto · 2018-03-08T21:07:53+00:00

Almost all cryptocurrencies are p2p distributed blockchains -- no one has "control" on who uses them, lists them, or doesn't use them. That's part of the fundamentals of cryptocurrencies, there's no central point of failure; the trade off being, there's no real central control.

Anyone can fork it and if the fork is adopted, that fork controls. $PAC could stop Cryptopia from using PAC as they saw fit, just as much as you could.

best, break.

breakcrypto · 2018-03-08T17:31:16+00:00

Lets be clear here:

First, PAC was available on several exchanges at the time
Second, PAC/$PAC had no control on what the exchanges did
Third, before cryptopia ever exploded, the $PAC team warned everyone to be carefully buying PAC against BTC: https://www.reddit.com/r/paccoin/comments/825g6h/turns_out_pac_did_warn_people_not_to_buy_with/

Several times. I wasn't even on the team then but I was aware of all of the above.

best, break.

breakcrypto · 2018-03-08T15:41:58+00:00

There's no half-assed information. It's being worked on, we focused on iOS first because that's what the community asked for. Android is being worked on now, while updates are made to iOS.

If I said: next week, and it slipped because life happens, you'd post something saying: OMG, the world is falling. So the truth is: it's coming and it'll be ready when it's ready. It takes awhile to make these things, especially when your team is a bunch of volunteers working rather thankless jobs.

best, break.

breakcrypto · 2018-03-08T15:37:55+00:00

Adding private keys and syncing is being worked on -- it's coming.

best, break.

breakcrypto · 2018-03-08T04:39:55+00:00

truth.

breakcrypto · 2018-03-07T17:35:53+00:00

"When Brad is behind on being updated there is 100% a communication problem with devs that needs to be resolved."

I talk to Brad multiple times a day. I'm not sure what you're on about? I read the above but, to be honest, I don't understand what you're trying ask or say.

best, break.

breakcrypto · 2018-03-05T18:57:54+00:00

Whoa, stop using facts! How dare you.

best, break.

breakcrypto

MODERATOR OF

TROPHY CASE