Bible Pay

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - MIP

Pages: 1 ... 10 11 12 13 14 15 16 [17] 18
Not sure how you can come to the conclusion Im here for the 1% or the botnet LOL :)

I was not targeting you in my comments, it was just an open thought.

My humble opinion:

Even though we know that helping orphans/distressed people is a comforting feeling, we must also watch for the investor interest.

Remember, no investors (mining, MN, traders...) = no coin = no help for the needy

The average investor is our friend, not our enemy. We don't have to scare or fear them, we need to manage them so there is no room for unnecessary greed, but for healthy returns.

To distribute wealth, first we need to create it. So I agree with some of T-Mike points.

I'm also for the staking-per-RAC idea.

It allows decoupling users from what other team members are doing (as it would happen with a relative number as magnitude). It can also boost the coin price and incentives to keep it instead selling it.

You add more CPU power = you must stake more BBP. 

We can even afford to change the number of BBP per RAC unit in the future as we see the evolution of this new PoDC system (for example if the overall RAC of the team surpasses the amount of BBP in circulation).

No, its not a PODC bug, we iterate through your UTXOs and honor the locks.  I would check to ensure you have re-locked your hot funds during each start.

Do you have a masternode.conf file set up with the Sanc's hot txid in it?

In one PC I do, but not in the other wallet with the sanc. controller address. So it's possible that for this wallet that UTXO was not locked.

I think we have a bug- PODC stake has used my 1550001 BBP of my sanc for staking, even if it's supposed to be locked


Now my sanc is "missing" :-(

Edit: I think it's because I cloned the wallet into another PC. Anyway, the lock enforcement should work at the blockchain level I think.

Our Japanese friend probably has already 10M, and if he was our famous "botnet" guy (I would bet on that safely), he probably made more than 700k a day on the previous heat mining phase.

Not much we can do against that, even introducing any staking schema (which is still a good idea on itself)

Well, do you suggest I delete the chains and resync? I'm pretty sure I'll be on your chain then.

I'm doing that, because my CPID 1BBP transaction disappeared and I'm back without registration... let's hope it works this time

Yes for sure. Been a busy week!
Looks like your explorer is down?

So the botnet will be kicked due to mandatory at block 33400.
But 33400 on our chain or the bot chain?

I would say that bot is already out of the "official" PoDC chain because we are getting our own confirmations (finally) and bot is 30 blocks ahead on its own chain. It can go on like that forever.

If bot tries to upgrade and hook to the "official" PoDC chain, he will mine by PoW until 33400 is reached (not likely as we are pretty close now).

I finally see my CPID after confirmations started working. However I want to separate the controller wallet for PoDC from the MN controller one, to another windows machine.

Can I run QT wallet on a new windows machine and re-associate to Rosetta, or do I have to "un-link" the current association first?
Thank you

Backup Block Explorer updated to v1.1.0.2c

I see three blocks numbered 33281 with their respective different hashes (?!)

On the unconfirmed, if you could double click it - if its an associate, please reassociate, if its a PODC update, just do a new one.

Those will probably stay unconfirmed forever - then later do a restart with -zapwallettxes

I did that, and the transactions dissappeared. But 5 minutes later they appeared again from nowhere and got a confirmation... interesting. No problem so far.

One of those was the 1BBP for CPID I sent 8 hours ago (42cad1f72d9b5578c6e67edd8fd2001d5312c930c5f5caa964e328b6b70dbbf1-000),

 I'll wait for 6 confirmations to see if CPID finally shows up.

EDIT: now I see the transactions as unconfirmed again... there must be a conflict somewhere

Alright guys, I think we are starting to be pressured into a mandatory upgrade.

Lict has raised a very valid point in prod - since I upgraded and the pool server, now the pool is enforcing the 1102 chain, which is causing questions.

So I suppose we need to hurry up and test 1102 and make a decision for release candidate.

I just checked my ca89 cpid association in prod and it was successful and I have utxo weight.

Luke, do you have utxo weight now?

Are we experiencing any other problems?

Im going to upgrade a few sancs now.

I have and the transactions I made a few hours ago show as "unconfirmed" (one of them is the 1BBP).

At this point I don't know which chain I am on. Is blockexplorer in the new one or the old one?

I already upgraded the MN without apparent issues though.

podcupdate gave true last night but my CPI is still not associated. I moved the cpid from my controller wallet to the sanctuary. Updating to the latest version now.

By the way, make -j4 doesn't seem to be doing anything, it seems to still use only 1 core.

I tried to compile once in a 16 vCPU with -j4 and -j8 and gcc crashed badly. -j2 worked fine though.

Yes, im on 33235 also.
Whats your exec getboincinfo output?

The same I posted some hours before

exec getboincinfo

  "Command": "getboincinfo",
  "CPID": "",
  "Address": "",
  "CPIDS": "",
  "CPID-Age (hours)": 422317,
  "NextSuperblockHeight": 33620,
  "NextSuperblockBudget": 760165,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 0,
  "Total Budget (One Week)": 0,
  "Superblock Count (One Week)": 0,
  "Superblock Hit Count (One Week)": 0,
  "Superblock List": "",
  "Last Superblock Height": 0,
  "Last Superblock Budget": 0,
  "Last Superblock Payment": -2,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0

The funny thing is that the CPID-Age (hours) is correct, but CPID itself is blank. Also I saw the 1BBP charge but as we have been in current block since then, transaction (e6e5d60e2c4d85d1e6f7ccec7dbae61ccacda8f9947b2d6a8277de2260c07206-000) is not confirmed yet.

I still don't see my CPID. My prod client says we are in 33235. Am I in the right chain? Do I have to upgrade/clean files? Thank you

Pages: 1 ... 10 11 12 13 14 15 16 [17] 18