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 - sunk818

Pages: 1 ... 11 12 13 14 15 16 17 [18] 19 20 21 22 23 24 25 ... 35
256
Archived Proposals / Re: PODC TEAM REQUIREMENTS
« on: December 04, 2019, 08:47:54 AM »
Since the second place in the poll (4 votes) is allowing any team with ^1.6 stake, is that option on the table? The selfish part of me wants to limit BBP earnings to just team BiblePay, but the other side says that if you want BiblePay to survive you want to expose it to any many people as possible. That's the mechanics needed to scale a product or service... so ^1.6 stake for any team seems like the better path. The ^1.6 stake is restrictive already, so why limit teams? If you do the analysis, for grcpool with a combined RAC of 749k (240k, 243k, 310k), you would need 1.4 billion to stake BBP. The exponent already limits the RAC whales (e.g. pools like grcpool, CharityEngine, boid, etc)

257
I do not believe I received the Kanye proposal funding,
I just created another proposal, should show up soon

===

All 3 nodes are running PrivateSend now

Im seeing this, havent seen any mixing yet:
https://i.imgur.com/FXI92Y3.png


I think we should get rid of PrivateSend. Who uses PrivateSend besides you? If many of the BBP features are based on coin age, PrivateSend mixing conflicts with those features (e.g. PoDC 2.0, Healing, PoG/Dynamic Whale Staking). How much development and support time is spent on this feature while the percentage of use is extremely low? If God knows everything we do, what do we need to keep private/obfuscated on the blockchain?

258

Just to clarify though Sun, you have been entering tickets in github with a lot of issues that have taken a significant [sic] amount of time that always ended up turning into non issues.  MIP and I have taken a look at this and already explained that there is no "Mac" format and his external purse collateral works fine on his macs.


You should be more respectful of our time.  I only asked for a regimented test because we have spent a considerable amount of time on these things in total.


I will admit some posted issues have been duds. We can't be 100%  ;D  all the time -- only Jesus. If you feel some issues are not worth investigating, then it is your job to prioritize or ignore them. I hope you can appreciate just how many issues don't reach you because many of us address it before it gets to you.


> always ended up turning into non issues.


Why would say "always". That sounds very dismissive of my contributions. I got tired so I had to stop before finishing...


Here are some issues I posted in the past that required fixing...


GSC Transmission for CameroonONE occurs even with -1
https://github.com/biblepay/biblepay-evolution/issues/26


One Click Mining Configuration corrupts biblepay.conf
https://github.com/biblepay/biblepay-evolution/issues/21


InstantSend not working - always confirms to 1 of 6
https://github.com/biblepay/biblepay-evolution/issues/17


Superblock Payment shows matured but requires 102 confirmations
https://github.com/biblepay/biblepay-evolution/issues/10


Runaway exception: bad lexical cast: source type value could not be interpreted as target
https://github.com/biblepay/biblepay/issues/102


One Click Miner Configuration writes tithing=1 instead of tithe=1
https://github.com/biblepay/biblepay/pull/87


exec bankroll: Signing transaction failed on locked wallet
https://github.com/biblepay/biblepay/issues/83


Invalid-tithe found from address xxx for amount of xxx
https://github.com/biblepay/biblepay/issues/81


Unable to mine... Cant sign block template with CPID - Error
https://github.com/biblepay/biblepay/issues/80


The auto-tithe feature was only tithing 90%.
https://github.com/biblepay/biblepay/issues/78


viewing PoG leaderboard causes crash if syncing blockchain <100k (pre-PoG)
https://github.com/biblepay/biblepay/issues/74


PoG Leaderboard - right click View makes QT wallet gets stuck
https://github.com/biblepay/biblepay/issues/73


PoG continues to auto tithe even though daily ~50k BBP donation was exceeded
https://github.com/biblepay/biblepay/issues/71


PODCUpdate: Unable to locate coins not marked as POG bankroll denominations.
https://github.com/biblepay/biblepay/issues/70


PoG Leadboard does show up in production
https://github.com/biblepay/biblepay/issues/67


1.1.5.4: InstantSend error: InstantSend doesn't support sending values that high yet.
https://github.com/biblepay/biblepay/issues/44

259
nevermind, I'm out of testing. This is no way to treat your testers.

260
Ideally, I'd like to just do an exec associate user verification code and that's all I need to do to join podc 2.0.


i prefer everything else is done for me (create cpk, joining wcg, etc) and it sends out the daily podc update as long I have the wallet running.

261
I don't think there is a Mac format; we have linux and windows file formats; To my knowledge MAC has migrated to the linux format; MIP has confirmed this is working.

Please work with MIP on this.  He's staking collateral successfully.

Edit:  Obviously the purse must be working because you sent out collateral before.  Can you please paste the output of 'exec boinc1'?  This tests the purse.  I think you are reading too much into the purse, and making an assumption.  Don't spend any time on the assumption, just paste exec boinc1 and we will go from there.  Macs file writing format works fine.

Btw, we no longer trigger sendgsc when the wallet opens.  Its only sent at the height shown in 'exec rac'.


biblepay.conf is in Mac format according to Notepad++. This is on my Windows 10 64-bit Home edition.


I can send you the file after I do exec createpurse.


the line ending is 0d0d0a instead of 0d0a . I think I mentioned this in the github. I didn't mention it because it didn't seem relevant, but if wallet is not reading biblepay.conf that creates all sorts of Issues I noticed in the past.



262



07:40:41

exec boinc1




07:40:41

{
  "Command": "boinc1",
  "purse amount matched": 599938.99127,
  "purse total": 645074.51811888,
  "txid": "b52b5a341e644a68823e3076b68b918325e11a9cb0e7ae3dfa795bef8a676e5a"
}


263

It might have been setting my wallet to be a privatesend liquidity provider and all the CPK keep going elsewhere.


My biblepay.conf kept saving as Mac format after the externalprivatekey got inserted by the biblepay code. saving it back as windows (crlf) seems to triggered a gsc tramission for cameroon-one, kairos, and wcg as soon as I opened the wallet again.

264
If you feel it is easy enough to use, then it must be me. I'll sit out testing as I personally feel all these steps are too hard for me to understand and follow.  :D


It might have been setting my wallet to be a privatesend liquidity provider and all the CPK keep going elsewhere.

265
If you feel it is easy enough to use, then it must be me. I'll sit out testing as I personally feel all these steps are too hard for me to understand and follow.  :D

266
I've been following BiblePay for the last 18 months, but if I'm having a difficulty time getting this work... this does not bode well for new members. Maybe I'm just dumb... Usability is critical, but adding complexity has only made the product more difficult to use.


I DMed you my exec rac output.

267
i'm giving up. I can't get my cpid registered. tried several times now.


exec rac works but haven't gotten a podc payments for days now.

268
Archived Proposals / Re: PODC TEAM REQUIREMENTS
« on: November 29, 2019, 12:26:36 AM »

I don't think it is too high at all.


https://gridcoinstats.eu/project/world%20community%20grid


Most of the top RAC "users" are pools. CharityEngine and grcpool.


Already, they are slightly split up so the RAC to BBP requirement is less.


Personally, I'd say blacklist any user above 100k RAC, but having the exponent discourage pool, people with high RAC hardware, or force you to split your cpid.


I also see BOID is another crypto BOINC pool.

269
couldn't the wallet version be enough to ban sanctuaries not on that version as well?

270
Bounty address changed to:


BKdkszSubBe9cNurd2LoBjPuaFhTL7utYw

Pages: 1 ... 11 12 13 14 15 16 17 [18] 19 20 21 22 23 24 25 ... 35