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 11 ... 25
46
Is there anything unusual about the current contract? The mag seems to be half on 2 of my wallets. I divided my RAC with the team RAC and it doesn't seem to be right.

47
How about 40 threads with sleep=1?   And btw what OS is this that keeps crashing?

Works fine until you try to change the # of threads in debug. Tried lowering to 20 and it crashed. Windows 10 Pro.

48
The pros are that smaller users need to be able to get into the coin for the coin to grow.  With little chance to successfully mine they'll move on.   For the most part, the coin would be healthier with 10,000 users with a Mag of .1 versus 100 users with a Mag of 10.

The cons are it introduces a complexity to the system that could be confusing or breakdown or be even seen as aggressive against new users.

Right now it's financially sound to PoDC with VPN, so the RAC will continue to rise rapidly until that point is exceeded.  The issue is that will further consolidate the coins into a few hands of the richest users as they are the only ones who can realistically afford a $300/day VPN bill.

Any system that is not linear will be cheated by users making multiple accounts to circumvent them, so while I think it is very reasonable that a high RAC user pay a larger stake/RAC than a small one, the reality is enough users will circumvent it to their own advantage.

I agree that the more users the better, I'm still thinking about how we can allow normal users to run PoDC without staking or being able to do  PoBH without having an active CPID. The technical knowledge required with PoDC is way over the head for many people

49
Yes that's quite true.
So I can't sleep... Using something other than linear can be circumvented with multiple accounts. So possibly there is no advantage there.

I was thinking though, when rewards are around 1.3 million daily, magnitude of 1 will earn 1300 BBP per day. We could set the stake to be N days worth of rewards at that magnitude. E.g 30 days. Magnitude =1, stake=1300*30=39, 000.
Magnitude 10, stake =1300*30*10=390,000
Mag 100, stake 3,900,000

So just for discussion, what are you trying to level the playing field. What's the purpose and pros and cons for the economy and for the rich and poor.

50
Hmmm, right, but they could RPC over SSL to the box and enter the pass without it going in the log, so Id rather not condone that behavior of typing it in if we can make it secure.  Let me take a look at how FTP allows the characters to be typed and see if I can make a headless test case.

So I see the miner appears to be a little more stable/faster with the last update- now we ask the miner to sign the threads cpids once and only re-sign if necessary (this keeps the lock from going off/on and prevents the crash).  Did 1110 prevent the crash for you in the miner?

Rob, appears to be better? I  opened with 6 threads and it seemed fine, switch to 8 in debug and it crashed. sleep=0.

51
I think its reasonable to require a 3 MM investment in order to control 160 magnitude out of 1000 (16% of the total rewards of the DC budget daily).  Thats the whole idea, to make it expensive to play if you have the guns to take share away from the rest of the community.

As far as Log rewards: thats the opposite of what this proposal is.  We want to Penalize you if you are taking all the others share.

Anyway, that 160 magnitude wont last long- it will be 80 then 40 in no time!  So 10K is not going to be too steep in just a couple months :).

I like magnitude much more than RAC - because its a share of the measurement relative to the community and not a squirrely sliding number that has no reference per day to the unknown total participation RAC.

It's good what you wrote, the whole point was to give more to lower computing power users. But to me, it's the same thing as saying we are going to penalized you for having too much money in your bank account!

I agree with Togo, if your going to stake, staking by RAC will result in more BBP being staked. With magnitude, you are limited to 1000*(whatever the community decides).

52
Oh good, sounds like something easier to deal with.  So, yeah biblepay-cli would log entries in the bash log because those are from bash.
Maybe if I send it like the FTP prompt, maybe it would not be logged.  I guess I can check into that in the morning.

In the mean time you want to try FTPing into a server with a password and see if bash does not log the pass as root?

The ftp password prompt is the like normal linux user login prompt so it does not log the password, it doesn't even display it when your typing it. But I mentioned in an earlier post that you are typing out your passphrase when you unlock your wallet normally anyways so i don't think it's a bigger security concern compared to before.

53
Ok 1.1.0.1 windows is out there now if you want to grab it.

I wont have any time left tonight to read the emails or PMs.

On "encrypted" are you referring to the UTXO message in the chain?  Sending Tx from user to another user is not encrypted, its signed.
The UTXO is also signed.  So it cant be hacked by falsifying a message in the chain.  PODC updates are Signed by your CPID.

Rob, no I mean the wallet has to be unlocked for podc updates. Right now it does not auto-unlock in headless.

54
Rob, I think we really need something for headless if the new UTXO proposal passes, leaving it un-encrypted is not a good idea.

55
Ok, thanks, I finally see the problem.  It was kind of a complicated issue, but Im pretty sure its going to fixed in the next version in two hours.

Sounds good Rob, I'll test it out. If you get a chance, I sent you some PMs, thanks.

56
My UTXO weight is 50556 :) so it looks like preparing but I don't know if 50556 is good or not.
Is it enough? Is it like UTXO 100 before? What would be there if my BBP amount would be less than 50556?
Thanks for clarification.

The new UTXO is not in effect yet, you just need 50,001 for 100% UTXO weight.

57
Biblepay - 1.1.0.9b
Mandatory Upgrade - for Entire Network (including Sanctuaries)

Before block 35110

- Avert mining crash and relay error messages in miner to getmininginfo
- Fix PODC association error (unable to sign cpid)
- Remove logging
- Fix getnetworkhashps
- Add unbanked CPID support
- Add configurable SPM (stake-per-magnitude) UTXO requirement (pending outcome of poll)
- Remove CompetetiveMining Tithe
- Added exec search key filter (Ability to search for DCC elements by CPID - IE exec search UTXOWEIGHT ca89)
- 7 Minute block targets as of block 35110
- Fix DC Superblock Budget as of height 35110

Updated both linux and windows just now.

Update:
Windows wallet still crashes basically on open with threads set to 6 and sleep at 0. Also tried changing the # of threads in the debug terminal and it also crashes immediately when I change it. With a lower thread number, it takes longer before it crashes but with 6 it crashes immediately.

58
Not to belabor the argument T-Mike but consider this.

A Mag of 160, means 16% of the daily reward will go to that user.  If the daily reward were just 1M / day (which is very sustainable for quite a while), then that is 160K coins per day.  At the 20K/Mag level, a 160 Mag user needs 3.2M Coins.  The other option is they could buy 2 MN with that, and get about...10K coins per day.   Requiring some sort of stake keeps people from jumping into and out of the coin as quickly.  That brings a stable user base.  That is good.

One minor modification I think would benefit all and solve the unbanked issue is since you need 1BBP to establish yourself on the wallet, what if we said that 1 BBP was enough for 1% UTXOWeight.  That would mean anyone with 1 BBP could get 1%, over time they could garner enough to get 100%.  The above 160 Mag RAC would end up with (if they got 100% for uptime) 1600 BBP the first day, and over a moderate time would be able to get 100% for Mag.

I don't think your argument of a 5% total stake of this coin will bring about stability. I would say you would need at least 50% of the total coin supply. If you can't reach that level, then all we are doing is purposely giving more advantage to average users. Which to say is not a bad thing, but I think people with high computing power will disagree.

We should at least do a log curve for the staking if this really passes. Also, I hope if only 20 people vote on the poll  we don't write this into stone, there should be a minimum number of votes. Not a lot of people are actually active on this forum.

59
Hi Mike-

I did download it I did open it, but unfortunately no lin crash dump or windows crash dump can point us to the line number crashing biblepay- except valgrind, or QT running in debug mode with symbols on linux, and I still havent ran it in valgrind mode as its a squirrely deal I cant reproduce it yet- although Im confident I will soon, just need to try to mine on my large vps.

So when you say one, does this crash for you when mining with more than one thread, or what is it that crashes it?

Im mining with 40 threads on my windows box.



EDIT:   I think I found the crash issue in the miner; fixing now...

Oh, that's great! Yeah anything over 1 thread the gui will crash.

60
Rob, I hope this helps. The wallet crashes with any values over 1 it seems like.

https://transfer.sh/12zRuR/Debug.zip

Password: biblepay

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