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 - T-Mike

Pages: 1 ... 5 6 7 8 9 10 11 [12] 13 14 15 16 17 18 19 ... 25
166
One comment, when I installed the windows wallet, the sanctuaries tab was hidden because of the PODC tab I think. I couldn't find it until I dragged the window larger. Someone new might have some trouble figuring that out. Now it just may be just me on my computer with the desktop configuration I have but I'm not sure.

167
Hmm, I dont think it requires a specific sending address to send funds though - can you instead go into coin control and see how much is available that is not locked?  It could be that all is allocated to sanctuary locked funds?

The receiving address that was on the Rosetta website did not have enough BBP in it. Once I put enough in, podcupdate shows true now. I actually had other receiving addresses on my account with BBP in them and none of them were locked except for the sanctuary wallet address.

168
Hi,

One of the Slovakian guys messaged me with an issue. i wonder if we can help. So I think this is the issue he is having:

Linux, commandline

1. He associated CPID to Wallet #1 (W1), he had receiving address RA1.
2. He wanted to change to wallet 2 (W2) with receiving address RA2. He typed
"exec associate mail pass true"
He received the message about welcome to cancer mining
3. The URL on this website https://boinc.bakerlab.org/rosetta/home.php
should be the wallet receiving address.
The URL matched RA2. Perfect!
4. He wasn't sure it had worked so he associated his CPID with wallet 2 again. This time there was a new address created and shown in the  https://boinc.bakerlab.org/rosetta/home.php site.
But he does not recognize the address. It is not RA1 or RA2. I checked, it is also not a mining address.
The question is, should this address on the boinc site be your receiving address of the wallet? Is there an error here?

5. He tried associating it again on another machine in QT mode. It worked fine and the address changed to his receiving address.


Seems that people may have issues if they associate CPID to the same wallet twice (by accident)

I also associated my account to the same wallet twice because I forgot it takes a while before the CPID shows up in the GUI. Oh, I see waht address your talking about now. I wonder if that's why I'm having issues, I don't have enough BBP in that address.

169
Looks like exec podcupdate has about 5 possible reasons to return false.   It should log the reason then return false.
So please try 'exec podcupdate' again, then immediately look at the log for the error.

Here is the most likely one:
   LogPrintf("\n PODCUpdate::Failed to Sign CPID Signature.  %s ",sError.c_str());
            

I believe that is happening when you dont have a CPID in the chain as of yet...


NOTE to all users:  You will never need to manually run exec podcupdate under normal circumstances; this is just to force it if your machine was off for long periods of time.


As far as the waiting for confirm:  Check the last block timestamp, its probably a lagging block.

** We just solved 33049; it probably confirmed

The transaction I sent myself is getting confrimations now. The error I'm getting is:

2018-03-05 04:06:47
 PODCUpdate::Error: Insufficient funds.

But there is plenty of BBP in my wallet. Does it have to be under a certain wallet address? This is in production by the way.

UPDATE:
I think the issue might be the receiving address that is associated with my CPID doesn't have enough BBP in it. Trying again now.

UPDATE 2:
podcupdate returned true. I didn't know it was only using a certain receiving address. Thanks guys!

170
It really should only say false if your wallet does not have enough funds to send 1 bbp out, or if its locked.
Could you please try a 'sendtoaddress YYYY 1" to yourself to see if that succeeds?

I used the GUI to send some to myself:
Transaction ID: edd8348af06de7463e3f95bf7381736581d4c03a932c3efee6f75b931bc3f974-000

So far haven't got a confirmation. But I did double check that my wallet is unlocked when I ran podcupdate.

UPDATE:
Looks like no confirmations after 13 min.

171
How do I debug "PODCUpdate": false? I updated my windows wallet about an hour ago. getboincinfo and getmininginfo both show no errors and the CPID is associated. OR does it say false because my CPID is already in the system?

172
"hashps": 74.40307451385468,
  "minerstarttime": "03-05-2018 02:19:07",
  "hashcounter": 296188,
  "pooledtx": 2,
  "testnet": false,
  "chain": "main",
  "biblepay-generate": false,

I think you said the wallet automatically starts with gen=1 right? So why is biblepay-generate: false

173
Archived Proposals / Re: Biblepay Charity Commission and Sanctuaries
« on: March 04, 2018, 09:12:24 PM »
Could the people who voted no please comment as to why you don't like this proposal?

174
The staking percentage command is suppose to be in the controller wallet config file right?

175
If you upgrade Prod now, your only issues is you will not be able to Vote yet (but dont worry about that as people will be upgrading and be in the same boat - and im upgrading the pool tonight for the sake of the proposal voting), and your heat miner runs a tad slower.  Heat mining seems to be a lost cause right now anyway.

After we have 51% of the sancs upgraded to 70716, voting works again.

OK, I'll try to update both later tonight or tomorrow morning.

176
Lol, I don't know what you mean, but I have been thinking about this too. I have an idea but need to thresh it out some more. Are you on slack/Discord?

I'm on discord. tmike. Has the new dev said anything? I haven't heard a peap from him.

177
I noticed my Hot sanc wouldnt start in 70716 (in testnet) until I cleared the data like West suggested, now my hot sanc is started and running 70716.

Thats good to know, because I really dont want to forcefully (cause Prod nodes to hang up on all prior version in prod unless we have to)...  so tomorrow, If we can start a few of our Prod  70716 sancs - and test them in prod to ensure they start in prod 70716 mode - then I think we can sail through Wednesday.

I always clear the files before I upgrade. So I'm a little confused about updating in production. Should I update my Sanctuary now? If I only update my controller wallet will I still get the rewards? I'm cautious because the protocol version is different.

178
9 testnet Sanctuaries running.

179
I hope they do, because Android tasks are pretty important for the real unbanked.  But I can also see if they have less than 3% of their users on it and I doubt there are too many people running more than a pair of Androids, but there are a bunch running multiple PCs.  Plus the PCs are doing much more work per machine on average, so I would be pretty confident in a guess that less than half a percent of the work is done by Android so it's likely not a high priority.

I was actually thinking the other day in the shower.....that there should be another way to make money than "mining". There's got to be a better way for the unbanked to participate in this new economy. Won't go into too much detail but I think you know what I mean.

180
https://boinc.bakerlab.org/rosetta/server_status.php

You can see there it appears they have run out of Android tasks

Application                    Unsent    In progress    Runtime of last 100 tasks in hours: average, min, max    Users in last 24 hours
Rosetta for Android    0           7508            6.54 (0.46 - 97.78)                                                                    793

Only about 3% use Rosetta for Android, and it pulls from a totally different set than the rest.  Windows, Linux, Mac, they all pull from either Rosetta or Rosetta Mini.

Thanks for the link.

https://boinc.bakerlab.org/rosetta/forum_forum.php?id=201

Lets see if anyone responds.

Pages: 1 ... 5 6 7 8 9 10 11 [12] 13 14 15 16 17 18 19 ... 25