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 2 [3] 4 5 6 7 8 9 10 ... 25
31
No, the daily emission amount of 1.19 MM is what it should have been, but due to cascading superblocks, we had a bug in the initial release so we left it in for 7 superblocks while the mandatory kicked in to Fix the calculation error.  It never should have been double daily payments.

Will the time between blocks be about what it is right now. 32.5 hours?

32
How do I associate my CPID with my other machines, So I can pool mine, without messing up the burn transaction on my PODC machine?

You can't, the CPID can only be used with one wallet at a time. You can copy the wallet to the other machines and just have one do the podc updates.

33
I really dont understand your perspective here MIP, I think my opinion is completely aligned with the investor.

Im Not here for the Miner, Im here for the small unbanked home PC driven average joe six pack and the investor.

Not sure how you can come to the conclusion Im here for the 1% or the botnet LOL :)

Sorry if I came across harshly Mike-T, I guess I made the assumption that you were biased because you own 20% of the magnitude.

Lets call a truce and start over with a clean slate.

Agreed Rob, thank you for the apology.

34
Archived Proposals / Re: PR, Communications, Marketing Proposal
« on: March 14, 2018, 02:34:33 PM »
Hi April,

I was thinking about your marketing-proposal in light on the new biblepay.org website that is up. In my opinion, the website could definitely use your touch, because it just seems disjointed right now in the way that information is provided.

I just read this medium article from Togo, which doesn't include the rosetta@home cancer research yet, but I think gives a more clear depiction of what Biblepay is about than the website does at the moment: https://steemit.com/cryptocurrency/@togoshige/biblepay-bbp-10-charity-cryptocurrency-masternodes-asic-resistant-cpu-mining-only

If you would consider working with Thomas (and maybe Togo, if he is willing) to really get the website to shine content-wise, I would absolutely vote 'yes' for that proposal. I'm also willing to provide content and/or feedback.

Hi,

Could you please give an update on the progress of PR? Thank you.

35
Today I did not receive a reward.  Looking at my tx history, no evidence of a PODC Update tx since 3.11.18 at 08:17 local time.  Was on 1.1.1.0, so upgraded to 1.1.1.1 (although was under the impression that was not required until Thursday).  Restarted wallet, ran exec podcupdate and got the PODC Update tx, but concerned why there was no tx in about 36 hours.

The only reason I can think of is if the wallet was locked or if you didn't have enough stake balance. I think you would need to go through the log file to find out.

36
You can use it from headless to check that the password was memorized.  Its just a sanity check.

Windows has been deployed if anyone wants to test it.

I think we are OK to release this afternoon, from what I can tell.

This latest version handles either poll outcome.

Id like to inform exchanges to upgrade late tonight, so please if anyone has any concerns please post, and please test anything remaining.

I'll upgrade both and let you know if I see any issues.

37
Biblepay - 1.1.1.1b
Mandatory Upgrade before block 35110


- Headless PODC Password support:
  ./biblepay-cli -headlesspodcpassword  <enter>     ,  then Enter password on next line.  Step 2 (optional): exec podcpasswordlength
- Added icon in QT for PODC Association, and icon for PODC Update
- Prevent wallet from spending Sanctuary collateral during PODC Update
- Add support for Required Stake-Per-RAC pending poll outcome


** Windows is compiling **

This is a prerelease, checked in now, available for linux.  It turns out this will need to be mandatory for the whole network due to that new 'potential' stake-per-rac feature pending the poll outcome. 

In the mean time if anyone wants to test the headless password prompt, go for it.
That's great! What is the exec podcpasswordlength for?

38
I commented in the other poll, but here is a short version of why staking per RAC is, to me, not workable.

Right now, if you stake per RAC at 10BBP/RAC, a 10K RAC machine would make roughly 15K BBP/day, and need a stake of 100K.  So 8 days to stake equity, much to fast in my thoughts.  But by the end of the year I expect us to be at 20M RAC and the reward will have dropped by about 12%, so the same 10K machine would make about 700BBP/day, or 150 days to stake equity.

Any system that doesn't slide based on the reward (which then becomes hard to understand) will be too generous to us now or too restrictive to us later.

The most fair system would be very hard to explain to new users, but would be some multiple of your daily reward held as stake, 100x or 150x spring to mind.  But coding that and presenting that in a way that could be easily to predict would likely be too complex for many new users.

I would argue that the most fair system is to not enforce staking at all.

39
Archived Proposals / Re: Poll for Type of Staking: MAG or RAC
« on: March 12, 2018, 02:59:54 PM »
I voted RAC but meant to vote MAG.

Here is why I think MAG is better.  Over time the RAC is going to be very high (my prediction is 20M RAC by the end of the year, if not sooner).  So if the decision is made to go on RAC it brings up the following conundrum.  Right now at 1.5M RAC, lets say we choose 10BBP/RAC.  While at 1.5M RAC, 10K RAC makes roughly 10K BBP/day.  So right now you'd need to stake (at 10/RAC) 100K BBP to make 10K per day.  The same machine at years end and 20M RAC would only make about 600BBP/day but still need a 100K stake.  So either the BBP/RAC is so low that people running thousands of dollars worth of VPS per month that there is no sacrifice needed to mine the coin, or it is at a reasonable number now but at years end will be entirely predatory to new users who have no real chance of making anywhere close to their stake in a year, let alone weeks.

Whearas going off MAG will be reasonably equitable.  The reward decreases over time (about 18%/year) and the RAC will likely be more evenly distributed (no one will likely have 10% by the end of the year). 

As far as the sub 1000 RAC, I think just saying an account with one ARM based is exempt is enough, otherwise people will divide their accounts and cheat the system.

The only other system I see is far more complex and would likely confuse users.  But the most fair system should be something like, you need 100x the BBP of your daily reward staked.  That sort of system scales well and is equitable.

I don't think ARM is enough,  not many people will want to use their phones to compute. Plus there is a huge iOS market that cannot run BOINC and the majority Windows novice computer users. In a couple of weeks or months 100,000 RAC might not give you that much reward. I'm not sure someone will want to create 100 VMs just to take advantage of the system. We can however change to perhaps 500 RAC, my Atom processor get 1000 RAC but that's running 24/7.

40
Archived Proposals / Re: Poll for Type of Staking: MAG or RAC
« on: March 12, 2018, 09:08:33 AM »
I don't think this is a good idea. If someone has an RAC of 10,000 they can circumvent stake by setting up 11 accounts.
Also, if I understand correctly, the unbanked on cell phones will need no stake.

Re this one "Do you want a static aggregate stake amount or a growing stake amount?  Unless I missed something Total MAG always is 1000.  So 1000*50000=50 million"
As I noted on the forum, this is not true, since even someone with magnitude of 0.1 will have to reach a minimum stake. It is likely that many/most of our users will be in this situation, hence the value would be more than 50 million.

I'd also like to note that this is currently the status quo; someone with RAC=10 needs to stake 50,001 to take fulla dvantage of their RAC. This is the same stake as someone who has RAC of 100,000. So there is actually no change for the small user, but a large change for the large user.

That is why I said to restrict the cpu type and os type. The filters I mentioned will drastically cut down on the number of people trying to do that. Realistically, its will probably be years before more then a couple people that are actually unbanked start computing.  There is hardly and cell reception in places like that most likely. We need to make it easier for normal computer users now in this time and place.

41
Archived Proposals / Re: Poll for Type of Staking: MAG or RAC
« on: March 12, 2018, 09:04:45 AM »
I would agree with no need to stake below 1000 RAC.  Limiting OS and processors would require a lot of code and time I would think.

It is already partially being done for the unbanked CPIDs so I don't think it will be an issue. It will take some time, but I don't think a lot, I could probably do the filtering part.

42
Archived Proposals / Re: Poll for Type of Staking: MAG or RAC
« on: March 11, 2018, 09:38:01 PM »
I'm thinking if the RAC is below 1000 you don't need to stake and limit it to Windows and Android machines and no Xeon processors.

43
Rob, is there a way to see which contract currently has the most votes? Thanks.

44
Running this upcoming contract on my sanc - I ran one about 2 hours ago:
'                        public key, cpid,                          magnitude, rosettaid, team, utxoweight, taskweight, rac,   unbankedindicator, utxoamount, RAC,   InductedCredit,

'BTjJENmWrQudFHEaqEpFg7ZeCA8HK2HwLW,e94c1704c75f731f8bfde303f08408ee,109.608,1981209,     15044,50001,       100,       976594,0,                  60.00,    178404,  107042

exec search utxoweight e94
  "E94C1704C75F731F8BFDE303F08408EE (03-11-2018 18:54:10)": "832822"


Looks like it has you at a mag of 109.6, with RAC of 178404 but its only giving you 60% based on UTXO weight of 50,001 see above, that gives only 107K rac, hence the lower mag.
Looking at your timestamp on the podcupdate - it looks like you send 832,822 in at 18:54 UTC time today (thats very recent, after my sanc ran its contract)

So hopefully you will be Hit by the old contract sancs today!  I guess the lesson here is to send the podcupdate a little earlier with the 500SPM just in case, so that its "in" earlier for the newer sancs.

Sorry but I have a family birthday party Ive got to go to and also got to run a long errand so I will be gone for about 5 hours.

Thanks for looking into it, hope you have a good time.

45
minersleep=1000 works for me.

And with that unlock.
At starting GUI wallet it asks me for password. I give there good password (I changed it, copy/paste, ...) and the wallet is still locked when it starts.
There is no error, only locked wallet (the lock icon is locked "wallet is encypted and currently locked", in menu is option "unlock wallet", in getinfo is "unlocked_until": 0, ... ). 
I must unlock it from menu then it works.

Are you saying it won't auto-unlock for PODC updates? Your wallet will be locked even after the prompt, it is only unlocked for the podc update.

Pages: 1 2 [3] 4 5 6 7 8 9 10 ... 25