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 - Rob Andrews

Pages: 1 ... 191 192 193 194 195 196 197 [198] 199 200 201 202 203 204 205 ... 263
2956
===
MINOR  UI:

- Move Proposals menu to a tab like Sanctuaries
---- Set Proposal List to be its own internal window
- Add Scrolling and Dragging abilities to Proposal List
---- or Find way to Shorten the information

===
QUESTION #1:
Should the Proposals Window also show other Governance information?

===
NICE TO HAVE:

--- Add Next Superblock Block Number (getgovernanceinfo: "nextsuperblock")
--- Add Superblock Budget Amount (getgovernanceinfo: "nextbudget")

--- Add Estimated Superblock Date/Time
(("nextsuperblock" - currentblock) * 7 min avg block time)

--- Add Visual Indicator or Sort/Separate Proposals based on if they are currently passing or not.
Example: https://dashvotetracker.com/

--- Add Full Budget Bar Chart (Total Budget and Currently Passing Budget)

===
HARDER:

--- Add ability to View Previous/Past Superblocks proposals/charts/info
--- Add Multi Bar Chart Split by Budget sections/types (IT, PR, P2P)

===
QUESTION #2:
- Add ability to Create Proposal to Wallet,
I assume we still need to wait on this?

============
IDEAS (NEED FEEDBACK):

- Pop Up / Notification
--- when New Proposal submitted?
--- Reminder to Vote on Proposals X days before end of cycle?
--- when Superblock is mined?
--- when Masternode leaves ENABLED state?

===
REFERENCES:

https://www.biblepay-central.org/en/proposals/
https://pool.biblepay.org/ >>> Governance >>> Proposal List

So taking a look at this list, 
on the minor UI:

- Move Proposals menu to a tab like Sanctuaries
---- Set Proposal List to be its own internal window
- Add Scrolling and Dragging abilities to Proposal List
---- or Find way to Shorten the information

we have Anton (Bezaleel) who volunteered to do this, so we are good here. 

On the Full Budget Bar Chart:
I have Bhavani working on our new Great Tribulation feature (thats the one where we have a Map of all Christians with longitude and latitude of the street corner they are near for privacy), so I think I can get Bhavani to add this Full Budget Bar Chart feature also.

On the Adding Proposals through the wallet itself:
I like the idea, it will help our decentralization.  Since I need to add some code to the pool to give it ability to pick up proposals entered through the core, I can take care of this feature. 


On everything else:  All I can suggest is if TheSnat wants to do them.  Snat, if you want to do the popups, there is a place in the code where we show a bible verse upon receiving BBP inbound.  You could potentially use that code to make these other pop ups, if you want.







2957
biblepaytest.conf
testnet=1
server=1
masternodeprivkey=xxx
masternode=0

-conf as a parameter to cdhoose different .conf file didn't work for me, but putting testnet=1 in biblepay.conf worked.

Using the -conf parameter is a way to get around adding all the other flags on boot (IE -testnet=1) etc.  But more importantly it allows you to set a different rpcport than your running prod instance.

Anyway if you put your biblepaytest.conf in your ~/.biblepaycore directory it should work. 
Start with

./biblepay-qt -conf=biblepaytest.conf

Also, you can put testnet=1 in your biblepaytest.conf, and leave it out of biblepay.conf. 


2958
I tested from QT Wallet, Tools >> Debug Console >>> stop, no issues

Ran command line daemon, waited for blocks to load and verify, ./biblepay-cli stop, no issues


Thanks, I strongly believe I caused the stop issue when I was working on the podc unlock feature.  It had something to do with asking the headless user for the password modally.  I remember I moved that feature over to the the biblepay-cli tool (so it would be on demand not modal).

Im pretty sure that fixed the problem on that day, so Ill close the stop issue for now.


2959
I took a look at the pull request. I was actually looking for a 'superblock payment' filter last week when I needed an overview of BBP payments for CameroonONe. ;D Awesome!

Unrelated: I've updated my Sanctuary to 1.1.3.4. Rob, are there specific things we need to test now?

I just released the latest version as a windows version also btw.


Let me see what test cases are left.


2960
Could someone do me a favor who is running the daemon and see if this has stopped happening?

https://github.com/biblepay/biblepay/issues/5


2961
I'll take a look at this pull.

Wow, nice work!  I actually thought you were pulling my leg all this time, I didn't know you actually knew how to program.

Great job dude!

Alright I merged it in and the next version is out there for Linux, but I have to get my son, so I don't think I can get windows out til tomorrow.


2962
Thanks for the list, I'm looking at the github commits and internally debugging the consensus feature, please hang on all.


2963
Archived Proposals / June 2018 IT Expense
« on: June 23, 2018, 04:20:09 PM »
The 1 year web hosting for www.biblepay.org + Togos exchange e-mail for 1 year just renewed, therefore I am requesting $263.76 for this expense:

http://pool.biblepay.org/SAN/expenses/June2018IT.pdf

?263.76/.002045=128977 bbp



2964
I submitted a pull request to for some simple UI filter options.  It seems there are a few more on github waiting to be merged /reviewed as well.

edit: re-enabled my masternodes on the latest ver.

I'll take a look at this pull.


2965
From Jaap
"
Both my rigs have been paid in the same daily superblocks it appears, but it says:
"  "Superblock Count (One Week)": 199,
  "Superblock Hit Count (One Week)": 6,"

The superblock count seems weird. Anyway, PODC-payments seem to be working. Are we still on one minute blocktimes? Because then there should me more like seven 'daily superblocks' each day, right?
"


Yes, its weird but its to be expected for various reasons so I dont find it alarming.
But yes you are correct, testnet blocks are still 1 minute, so we would normally have 4 superblocks a day etc.
However, we only have 3 sancs running out of 20, and up to last night 2 of my 3 were down or on the wrong version.

But analyzing closely, the mature consensus part is working and we are generating superblocks when all 3 of us come online.

I just ran exec testvote on 2 of mine, and I can see from exec podcvotingreport, the next boinc superblock will emit.

Anyway, Im glad you mentioned this regardless, because I do see one feature we really need to squeeze in this mandatory, so thanks!
We now have (as of the next version) we have a locked consensus on the CPID list (as of 4 hours prior to the quorum), we have locked UTXO list, and the quorum is using the same source data, so it is close.  However, I do see that we have a staggered schedule set up for downloading the rosetta data (Its more of an issue where the local client is honoring the file for up to 24 hours to save bandwidth).  Im going to look into making our mature consensus attempt to pull the files at exactly the same 4 hour window across sancs and get this in the next version.  (I noticed this recently, that some of the CPIDs has slightly higher rac on one of my sancs, and then I realized whats happening with the cache rules).

We need to reach out to Bhavani to see if he will take care of any of Togos UI bullets.  Togo, were you going to make a list of the top 5 requests?


2966
Upgraded to v1.1.3.3, re-enabling my sanc

Ok, Im up to 1133 on my two sancs now.

Have you guys been getting paid daily superblock rewards?  I got one while my sanc was off.

So btw, an update on the proposal filter feature:  Its in this version, but as you can see in proposals list, both are still there even though the Groundbreaking one was paid.  I took a look at this in depth, and what it is is that since the supermajority of the sancs went down (Or were not running watchman), they lost the trigger that links the proposal to the trigger to the superblock.  Another words the chain cant see that it was paid.  I was taking a look at this in prod, and I dont think this particular thing can happen with 100+ sancs on line.  So I wrote some debug info for the feature and what I think Ill do is when we deem proposals safe to enable in prod (IE the next leisure release), we can log in on the prod side and test it.  But from what I see from the debug info, it should work in prod as-is and filter paid proposals in prod.


2967
Fund update:

I've sold about half of last months BBP for BTC on southXchange and QIEX. Someone seems to have put up a 3M BBP sell-wall on southXchange (I saw the wall move from 40 to 34 Satoshi). My sell orders are above that, so since the wall arrived I haven't sold BBP anymore.

Anyway, that's the update :) Of course, the Fund has paid 1 BTC for CryptoBridge and now we're saving for other future exchanges.

I'm going to ask for another round of 'one Sanctuary worth of BBP', so 1.552.501 BBP (one sanctuary + proposal costs).

Code: [Select]
gobject vote-many f852c5ea1ddaac70e991b97814f28a1852a61ebbae9a595f8b524de6c4515322 funding yes

Great work keeping this treasury topped off.

I think our exchange future is bright, after cryptobridge,  (hopefully NEXT also) and then coinexchange.io, I think we will have double the investor presence.

I have a suggestion, this is sort of a caution.  Since none of us know the future price of the market (IE market timing is impossible to know), nor do we know the future price of bitcoin, I recommend dumping coins that are over 30 days old on the exchanges so as to keep the situation moving.  Obviously if you have the time and patience to do so slowly (IE 200K per day or something) then that is even better.  But my suggestion stems from this:  I would not want to see 3-6 million coins get backed up and unsold for 60 days while waiting for a better price.  Because what can happen is two very bad things:  Price could drop leaving us with nothing, and coinexchange.io could withdraw the deal (they have been known to if we wait too long).

So this is not a rule just a friendly recommendation that it would be better to flush them out each month and let the value buyers buy them up even if we have to take a hit.  I feel that over time, all this averages out for us.



2968
I just deployed 1.1.3.3.

Please upgrade all testnet sancs so we can test the mature_consensus feature for the daily PODC superblock.

Its OK if non participating sancs are not upgraded; we only need a few that are actually online and synced to make this work.

(I think we had 3 sancs as of yesterday running out of a list of 20 with 17 offline).

(We need 2 for a consensus).


2969
Archived Proposals / Outbound Letter Writing Reward Refill
« on: June 20, 2018, 04:42:23 PM »
All,

We had pretty good success using the last 500K letter writing reward bounties, we wrote 107 outbound letters and paid a reward between 3400 bbp and 1350 bbp, but the money is being eaten up quickly (we spent 450K out of 500,000) so we have about 50K left.


Yes, we still need to implement the orphan adoption system, where a miner can adopt an orphan and have a closer relationship.  That is still coming, this is a stopgap in between.   The technical reason that has not been programmed yet is we have been hit with two high priority feature requests (Monthly expense totals for charities in the pool, and the ability to store tax records for bloom, compassion and cameroon one in the pool).  Once these are out of the way we will jump back to orphan adoption.


In the mean time lets vote for a refill so we can keep the writing going the old fashioned way  ;D.


2970
Archived Proposals / May 2018 IT Expenses (Payroll)
« on: June 20, 2018, 01:22:06 PM »
To partially fund some of my own programming hours, I would like to submit Github commits for the core biblepay wallet from Feb 1 2018 through Feb 28 2018:



Commits on Feb 26, 2018
1.0.9.5b-Leisure Upgrade  …

@biblepay
biblepay committed on Feb 26
 
1.0.9.5-Leisure  …

@biblepay
biblepay committed on Feb 26
 
Commits on Feb 23, 2018
1.0.9.4d-Leisure Upgrade  …

@biblepay
biblepay committed on Feb 23
 
1.0.9.4c-Leisure  …

@biblepay
biblepay committed on Feb 23
 
Commits on Feb 22, 2018
1.0.9.4b-Leisure Upgrade  …

@biblepay
biblepay committed on Feb 22
 
1.0.9.4-Leisure Upgrade  …

@biblepay
biblepay committed on Feb 22
 
Commits on Feb 20, 2018
1.0.9.3d-Leisure Upgrade  …

@biblepay
biblepay committed on Feb 20
 
1.0.9.3c-Leisure Upgrade  …

@biblepay
biblepay committed on Feb 20
 
1.0.9.3c-Leisure  …

@biblepay
biblepay committed on Feb 20
 
1.0.9.3b-Leisure  …

@biblepay
biblepay committed on Feb 20
 
Commits on Feb 19, 2018
1.0.9.3-Leisure  …

@biblepay
biblepay committed on Feb 19
 
Commits on Feb 17, 2018
Update biblepay_zh_CN.ts and biblepay_zh_TW.ts  …

@jguan
jguan committed on Feb 17
 
1.0.9.2c-Leisure  …

@biblepay
biblepay committed on Feb 17
 
1.0.9.2b-Leisure Upgrade  …

@biblepay
biblepay committed on Feb 17
 
1.0.9.2-Leisure Upgrade  …

@biblepay
biblepay committed on Feb 17
 
Commits on Feb 14, 2018
1.0.9.1b-Leisure  …

@biblepay
biblepay committed on Feb 14
 
1.0.9.1-Leisure  …

@biblepay
biblepay committed on Feb 14
 
Commits on Feb 13, 2018
1.0.9.0f-Leisure  …

@biblepay
biblepay committed on Feb 13
 
1.0.9.0e-Leisure  …

@biblepay
biblepay committed on Feb 13
 
1.0.9.0d-Leisure  …

@biblepay
biblepay committed on Feb 13
 
1.0.9.0c-Leisure  …

@biblepay
biblepay committed on Feb 13
 
1.0.9.0b-Leisure Upgrade  …

@biblepay
biblepay committed on Feb 13
 
1.0.9.0-Leisure for Prod  …

@biblepay
biblepay committed on Feb 13
 
Commits on Feb 12, 2018
1.0.8.9d-Leisure  …

@biblepay
biblepay committed on Feb 12
 
Commits on Feb 10, 2018
1.0.8.9c-Leisure Upgrade  …

@biblepay
biblepay committed on Feb 10
 
Commits on Feb 9, 2018
1.0.8.9b-Leisure  …

@biblepay
biblepay committed on Feb 9
 
1.0.8.9-Leisure  …

@biblepay
biblepay committed on Feb 9

Commits on Feb 8, 2018
1.0.8.8q-Leisure  …

@biblepay
biblepay committed on Feb 8
 
Commits on Feb 7, 2018
1.0.8.8p-Leisure  …

@biblepay
biblepay committed on Feb 7
 
1.0.8.8o-Leisure  …

@biblepay
biblepay committed on Feb 7
 
1.0.8.8n-Leisure  …

@biblepay
biblepay committed on Feb 7
 
1.0.8.8m-Leisure  …

@biblepay
biblepay committed on Feb 7
 
Commits on Feb 6, 2018
1.0.8.8l-Leisure  …

@biblepay
biblepay committed on Feb 6
 
1.0.8.8k-Leisure  …

@biblepay
biblepay committed on Feb 6
 
1.0.8.8j-Leisure  …

@biblepay
biblepay committed on Feb 6
 
1.0.8.8i-Leisure  …

@biblepay
biblepay committed on Feb 6
 
1.0.8.8h-Leisure  …

@biblepay
biblepay committed on Feb 6
 
Commits on Feb 5, 2018
1.0.8.8g-Leisure  …

@biblepay
biblepay committed on Feb 5
 
1.0.8.8f-Leisure  …

@biblepay
biblepay committed on Feb 5
 
1.0.8.8e-Leisure  …

@biblepay
biblepay committed on Feb 5
 
1.0.8.8d-Leisure  …

@biblepay
biblepay committed on Feb 5
 
1.0.8.8c-Leisure  …

@biblepay
biblepay committed on Feb 5
 
1.0.8.8b-Leisure  …

@biblepay
biblepay committed on Feb 5
 
1.0.8.8-Leisure Upgrade  …

@biblepay
biblepay committed on Feb 5




For a grand total programming time of
   (42.5 hrs per week * 4 weeks) = 170 hours @ 40.00 per hour = $6,800.00

Also, I would like to expense the following IT expenses for Biblepay:


For a Grand Total Proposal of :  $6,800.00
Equaling:

?6800.00/.002371 (CoinMarketCap 6-20-2018) = 2,867,988 BBP


Thank you for your consideration.

Pages: 1 ... 191 192 193 194 195 196 197 [198] 199 200 201 202 203 204 205 ... 263