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.


Topics - Rob Andrews

Pages: [1] 2 3 4 5 6 7 8
1
This idea stems from the desire to appeal to a large user base (IE mass PR/Advertising), without paying a lot of advertising dollars per new user, new user retention, and price appreciation.


What this theoretically does right off the bat is makes BBP more valuable, because we can set this up to ensure that at least the same value of BBP locks up an equivalent or more amount of DASH.  For those who do it, they receive the interest reward.  Those that dont are 'out of the loop' and they will strive to either do it or maybe exit and sell off the coins.

- Doing this would theoretically mean unlimited popularity - since this would appeal to the Entire Dash Investor group
 (I believe this would be more than 100,000 distinct users).  The appeal is, we are saying IF you hold a DASH UTXO, and a BBP UTXO, you receive the DWS reward (about 30% ROI).
I think a lot of Dash investors would consider doing this, because that means earning BBP on their DASH without liquidating DASH.
- Elements of a stable price (currency backed by another currency).  Since BBP would lock up an equiv. amount of DASH, theoretically our price would rise as more and more come in to buy more BBP to lock up dash.
- Rewards for the Dash investor base that currently do not receive rewards.
- Higher interest rewards for BiblePay users who diversified over more than one currency:  This is because with POOS coming, a lot of sancs have no avenue to earn rewards.  With DASH backed rewards, they can put that BBP in the Dash-BBP bucket.
- A 'non participation penalty' for coins that sit for sale on exchanges
- Diversification:  This makes BBP much more like a stablecoin.  This means if you hold $1K of BBP and $1K of DASH, and earn 30% per year, you have twice the chance of weather a crypto-meltdown than if you simply hold one currency.  It might also bring some positive reputation to BIBLEPAY also, to be yoked with DASH much more tightly.
- In wallet - your keys - so you control the security on this - and you do not have to give up your DASH keys or your BBP keys
- DASH has 560% new users in Venezuela this year - and this goes hand in hand with our initiative to provide a stipend to VZ citizens to help them (IE a weekly bread allowance in BBP)
Also our ties with "dashpay" allow users of BBP to spend DASH - therefore we have a positive relationship in spending BBP to dash merchants also.


Here is theoretically how this system would work:


BBP would strive to ask users to lock every UTXO with a matching DASH UTXO of equal value or more, in order to create a contract for that UTXO. 
(They would click a command that locks the Dash UTXO-Priv-Key against the BBP-UTXO-PrivKey creating a contract - and at that particular time the DASH UTXO must be greater in price than the BBP UTXO they hold - IE $1050 for Dash and $900 for BBP is OK for a duration of say 90 days).   The BBP wallet would record a current interest rate reward (depending on how long the lock is).  BBP would constantly monitor both the DASH UTXO and the BBP UTXO.  If either is spent, the contract will be nullified.  However, if neither is spent, each month, the BBP user would receive a reward automatically from the coinbase - containing the interest component.  The Lock would continue in place until the duration expires.  (So a 6 month lock would equal 6 coupon payments).

For security purposes, we would not ask the Dash user to give us their private keys - instead we will have them sign the UTXO from the dash wallet using a command we provide, and they will paste the sig into the bbp command.  This will prove ownership of the UTXO on the BBP side- then we will monitor it until its spent.  On the BBP side we will sign their UTXO ourselves and put all this in a contract.

The BBP wallet would pull information from the DASH network to know about their UTXOs automaticaly, and memorize them.  It would then REJECT new contracts that are attempted on spent UTXOs automatically.  Anyone who spends a DASH UTXO mid contract would cause cancellation of the contract, therefore they would lose the upcoming dividend strip.

One thing I like particularly is the free advertising.  Its very difficult to advertise a crypto without paying massive coinbase emission or campaign fees. 

Note that I am not creating this because I hold any DASH myself.  I actually dont have much DASH right now, but I would be willing to do this myself as I can see the value in gaining diversification away from the USD and into dual-cryptos at once.



2
Bounties / BiblePay Forum Activity Rewards
« on: August 09, 2020, 02:30:14 PM »
I am interested in attracting more than one new user to our project per day, therefore we will be offering forum activity rewards.

In this beginning stage, lets call this the beta testing stage, the program will be limited to activity posted in this thread (the op post thread) :
https://forum.biblepay.org/index.php?topic=517.285

The way it works is our foundation will send you a wallet reward, based on the table below, according to your activity and benevolence.

To get started please follow these steps:

1) Join forum.biblepay.org and create an account so you can post in the above thread.
2) Add your biblepay wallet address to:   https://foundation.biblepay.org/AccountEdit
Populate the Forum Rewards (BiblePay receive) address field.  Click Save.
3) Ask questions about biblepay in the above thread, and/or help other users.
(https://forum.biblepay.org/index.php?topic=517.285)
4) Thats it!  We will assess the rewards automatically once per week.

Please see the following chart for the reward levels:

(Note the post count is the Distinct post count made by the user (deleted and/or reported posts and/or flagged as negative do not count) in that particular Week, and must have positive benevolence, and the posts must be in the OP thread listed above):

Reward = budget_factor(available_budget) *  min((Benevolence/10),1) * 1000

Example:
4 posts with a benevolence of 1 = 4,000 bbp
1 post with a benevolence of 20 = 2,000 bbp
1 deleted post = 0 bbp


To see your benevolence, please see your avatar on any of the forum threads.


PS:

We will create a report that outlines the summary of the payouts per week; this will let you know the rewards you received (and the community received).











3
Bounties / BiblePay Mass User Expansion - New Forum User Bounty
« on: August 08, 2020, 01:31:39 PM »
We are pleased to offer a bounty of 20,000 BIBLEPAY for new community members-- please follow these steps:

1)  Register a forum account here at forum.biblepay.org, and change your avatar to something other than the default
2)  Download the Core wallet from here (not the mobile version), and sync it:
https://www.biblepay.org/wallet/
3)  Read our OP post, and then Make a post containing a question about biblepay here:
https://forum.biblepay.org/index.php?topic=517.285
4) From the core wallet, click Tools | Info | Console:
From the console, type the command: faucetcode
Paste the faucetcode here in this thread, and then one of our mods will review the steps and pay you the reward.

Thank you for joining BiblePay.





4
Production Proposals / Monthly Superblock Budget Change
« on: August 04, 2020, 09:21:39 PM »
Since we voted that sanctuaries will sponsor orphans starting in the next mandatory, this means that Sanctuaries are paying the lions share of the charity expenses in the future.

This means that BiblePay should not pay the primary charity expenses from the monthly governance superblock (this is approx. 10% of the coins emissions).

I propose that we reduce the monthly superblock budget (by removing the charity component) and apply it to the coinbase reward, and we raise the sanctuary portion of the coinbase (approximately to the proper percentage that rewards this amount primarily to the sanctuaries).

This means the monthly budget will drop to 4.8 million (from 9.7 million) - and we will clarify the breakdown on the website to:
8.75% - Monthly governance:
- 50% IT
- 25% PR, P2P
- 25% Miscellaneous

And the 8.75% would be added to the sanctuaries, bringing their reward up to 41.25% (from 32.5%).






5
Production Proposals / Automatic Price Mooning
« on: July 21, 2020, 09:28:10 AM »
I'd like to discuss the design and viability of a new feature, something that might be called Automatic Price Mooning, or Moon Ratcheting or maybe something catchier.

The idea stems from the question, What will make investors most interested in buying and holding BBP?
I thought of creating a built in trading mechanism that requires BBP to buy coins off the open market each month, (with the intent that if we have an increasing volume and an increasing price, it would provide impetus), but the downside to that idea is that in order to raise capital to pay sancs to buy on the open market we have to sell our own currency which further exacerbates a bigger sell wall on SX (which imho, we need to get rid of at this point, not make it worse).

So the best idea I have at this point is to make an algorithm that Records our current price in Satoshi (down to the 9th digit), so today for example our price is .000000015 at the daily GSC superblock height, once per day.  (And, we will remember the last 7 days of prices in memory also).

What we would do is simply have two rules:

If the snapshot price is Less than Yesterdays snapshot price, OR Unchanged from Yesterdays snapshot price, we pay all blocks at 7 BBP for that day.  (Meaning that the sanctuaries and the miners get shorted by 99% of their reward that day).
Otoh, if the snapshot price is HIGHER than yesterdays snapshot price, even by .01 satoshi, we emit our normal rewards for that day.


So the marketing on this is IF BBP does not have a continually increasing price in Satoshi, we pay 99% less rewards to the Sanctuaries and to the Miners.
This would give an impetus for someone to step in to SX and buy up at least enough to get us to the next satoshi higher.

I think its a pretty strong impetus to keep the price rising (hence the name Automatic Price Mooning).

Obviously when we hit a high barrier like 7 Satoshi, we would waver for a couple weeks at 7 to break through to 7.1 etc.
Of course the downside is the sanctuaries would get strong cuts along the way, but remember since everything is relative, a higher price per coin * existing supply is still equal to a higher reward than more coins * less price (VALUE = COUNT_OWNED * PRICE).

The main viability of this idea is actually on the question, will more net miners and project participants enter BBP as they see the price rising to real levels - levels where people take this project seriously.

I don't believe this idea will in any way hurt our security, because we are rolling out fully locked LLMQs with chainlocks in testnet (this means the sancs constantly monitor the order of the blocks), so lack of payment with merge-mined blocks should not pose any security risk to the chain.  I think the entire effect will be on those who receive rewards wondering why they got 1 bbp instead of 3000 etc.

And lets think of a really bright outcome:  What if this wild idea gains national attention?  Price Mooning?  What if a lot of people jump in and say, BiblePay is breaking through with this strange feature.

On a side note, we would leave the monthly governance emissions the same during the variable emissions phases - simply because we do not want fork risk.  The gov emissions are precalculated in many places and shorting those proposals down to 1 bbp causes too many problems.  However note that we will have proposal in soon to reduce Governance expenses down dramatically (since governance is no longer paying for charity) and we can give that portion to the coinbase reward so the sancs get more of a reward (and that helps them pay for POOS).


Please, if you have improvement or suggestions or downsides, please let us know.  Im willing to change the idea, but obviously it has to be able to work without fork risk.

EDIT:
Btw, BBP would save 1.8MM per day on emissions when implemented (or 45MM per month).  So there is a real theoretical impetus for a rising price when less coins are minted that would ultimately be sold.


6
SITIO WEB | GITHUB | EQUIPO | CRONOGRAMA | LIBRO BLANCO(Being Updated)

FORUM | TWITTER | REDDIT | DISCORD | FACEBOOK | TELEGRAM

 Minería combinada RandomX provee a los mineros de dos fuentes de ingreso, a la vez que previene de GPUs y ASICs.

 Prueba  de Computación Distribuida (PODC, por sus siglas en inglés) permite que la potencialidad de la blockchain sea utilizada de manera productiva, invirtiendo en la investigación y desarrollo humanitario de las ciencias, en la búsqueda de una cura para el cáncer, SIDA y malaria.

Lanzada en Julio de 2017 por Rob Andrews sin ICO ni preventa, Biblepay es un proyecto criptográfico  descentralizado y autónomo que dona el 10% a los niños huérfanos del mundo a través de un sistema de gobernanza basado en Nodos Maestros (Masternodes, acá llamados “Santuarios”). Ansiamos compartir las Buenas Nuevas de Jesús, por lo que hemos compilado en su totalidad la Biblia del Rey Jacobo (versión KJV) en el código fuente de la billetera. BiblePay (BBP) es una criptomoneda de características deflacionarias, por lo que su emisión disminuye en 19.5% anualmente.

El Proyecto puede ser descrito como una utilidad: un método alternativo para realizar donaciones a la caridad. A través de losContratos Inteligentes Genéricos (GSC, por sus siglas en inglés), el Proyecto tiene el propósito de llegar a ser la billetera de confianza de la Comunidad Cristiana a nivel mundial. En el futuro, el equipo pretende lograr la reducción en el espacio requerido para el funcionamiento de los Santuarios e incorporar características corporativas de integración, por ejemplo, acceso del lenguaje C# a la cadena de bloques. La plataforma de BiblePay es una criptográfica derivativa de Dash-Evolution. Ubicados en Dallas, Texas, nuestro objetico es ayudar a los huérfanos a nivel global. La Hoja de Ruta puede encontrarse en: wiki.biblepay.org/Roadmap


Entrevista | Podcast | Youtube | Medium | Steemit | Newsletter





Logros:

- Más de $220.000 donados a la Caridad!

- Más de 30.000 años de procesamiento de datos (CPU) donados a la investigación contra el cáncer.
 
- Más de 100 huérfanos patrocinados cada mes!



Descripción:           

Información Nutricional     

Dimensiones     

BiblePay Evolution

Novedades:

Contratos Inteligentes Genéricos (GSC)

Prueba de Patrocinio a Huérfanos (POOS)

Prueba de Computación Distribuida (PODC)

Staking Dinámico (DWS)

Gift Card de DashPay



Utilidades:

DashPay – Compra Instantánea de Gift Card con BiblePay (usando Dash, InstantSend y Bitrefill)
wiki.biblepay.org/DashPay_RPC


“Ordené una Pizza con BiblePay” - Historia
Pizza Delivery





Teología

Carta al Rezagado (para aquellos que se quedaron en El Rapto):           https://san.biblepay.org/Theology/Left%20Behind%20Letter.pdf





Descargar Billetera:

biblepay.org/wallet


(Actualizar y restaurar la Billetera)




      

(Verificar Hash)

Windows 64 bit - biblepay.org/biblepayevo64.exe (Hash)



Mac OSX - biblepay.org/biblepaycore-evo.dmg



Linux GUI 64 bit - biblepay-qt-evo-x86_64-pc-linux-gnu.tar.gz  (Hash)

Linux CLI 64 bit - biblepayd-evo-x86_64-pc-linux-gnu.tar.gz  (Hash)




Código Fuente- github.com/biblepay/biblepay/blob/master/BuildBiblePay.txt



Billetera de Papel - biblepaywallet.github.io



Billetera Móvil:

   

Android - play.google.com/store/apps/details?id=com.biblepaywallet

iOS - apps.apple.com/us/app/biblepay-wallet/id1467714837



Guías de Minado:

Prueba de Computación Distribuida
wiki.biblepay.org/PODC_Setup

Prueba de BibleHash
wiki.biblepay.org/POBH_Setup

Pools de Minería:



Estado del Pool
miningpoolstats.stream/biblepay



Obtén Monedas:

FreeFaucet.io:
freefaucet.io/claim/index.php?coin_name=biblepay&faucet_key=freefaucet18&claim=Claim

Faucet SouthXchange:
southxchange.com/Balance/Faucet

Campañas de Sanación (Entradas en Diario):
wiki.biblepay.org/BiblePay_Healing_Campaign

Programa de Caza de Bugs:
forum.biblepay.org/index.php?topic=408.0

Solicitar Fondos del Sistema de Presupuesto Mensual para su trabajo (Sistema de Propuestas):
forum.biblepay.org/index.php?board=5.0



Exchanges:

coinmarketcap.com/currencies/biblepay/markets/

coingecko.com/en/coins/biblepay/trading_exchanges#panel









Explora la Blockchain:







Socios/Colaboradores:






Especificaciones:

Lanzado en: 23 de Julio de 2017
Algoritmo: Prueba de BibleHash (POBH)
Estrategia de Minado: solo CPU(Resistente a GPU/ASIC)

Sin Pre-minado / Sin ICO

Tiempo Objetivo por Bloque: 7 Minutos
Bloques por Día: 205
Velocidad de Transacción: Admite InstantSend

Suministro Máximo: 5.2 billones de BBP para el año 2050

Características de Circulación: Deflacionaria
Tasa de Emisión: -1.5% mensual (19% de deflación acumulada al año)

Cronograma de Emisión:
wiki.biblepay.org/Emission_Schedule

Gestión Económica:
wiki.biblepay.org/Economics



Recompensa por Bloque:
https://www.biblepay.org/#Technical%20Details



Santuarios (Masternodes):

Para reducir la presión de venta sobre nuestra criptodivisa, cada uno de nuestros Santuarios debe patrocinar (estadísticamente) a un huérfano, de acuerdo a nuestro algoritmo de Prueba de Patrocinio a Huérfano (POOS).
 
Adicionalmente, liquidamos el XMR recaudado (a través de la Minería Combinada XMR-BBP) para los gastos de la Caridad restantes.



Sistema de Gobernanza & Presupuestos:
- Entendiendo la Gobernanza
                                                                   
Requirimientos Colaterales:
4.500.001 BBP

 

Estadísticas:
- Masternodes.Online
- Masternodes.Pro
- MasterNodeCap
- Masternode.Live
- Masternodes Buzz
Setup:
- Guía Paso a Paso
- Script para Instalar con 1-Click
- Ascender a Determinista
____________________________

Monitoreo:
- NodeCheck.io



Caridad:
**  Sólo contribuimos con organizaciones de Caridad que estén sobre el 75% en eficiencia, por lo que más del 75% llega directamente  al beneficiario. **

 



Contabilidad:
- accountability.biblepay.org
- Investigación Pública



Social:

Foro      - forum.biblepay.org
Twitter     - twitter.com/BiblePay
Reddit      - reddit.com/r/BiblePay
Discord    - discordapp.com/invite/yWgbKdM
Facebook  - facebook.com/BiblePay
Telegram  - t.me/biblepay_airdrop

            



ADVERTENCIA: "A pesar de las características deflacionarias de BiblePay, es imposible garantizar un ROI positivo frente a las principales criptodivisas inflacionarias. Los rendimientos pasados no son de ninguna manera indicativo de posibles rendimientos futuros. Somos una utilidad, y no una garantía. Por favor abstenerse de invertir en BiblePay antes de informarse respecto de los riesgos involucrados en las criptomonedas. "



Anuncio Original (Inglés)

Segundo Anuncio (Inglés)








Links al Libro Blanco:

Libro Blanco (Chino)- https://san.biblepay.org/Mission/BiblePay_WhitePaper_Chinese.pdf



Reglas del Foro:

1. Absténgase de hacer suposiciones  de cualquier tipo si no está 100% seguro. En este caso, deberá indicar claramente que se trata de un comentario u opinión, por ejemplo: "En mi parecer…." o "Considero que…". Tenga especial precaución respecto a publicaciones de arácter técnico, ya que cualquier desinformación podría dar ideas equivocadas a los inversores.

2. Mantenga un tono y lenguaje agradables, sea cordial y agradecido. Evite el lenguaje ofensivo.

3. Tenga disposición de investigar o trabajar, así como de compartir de su experiencia con la comunidad, o encontrar a alguien que pueda hacerlo. Este proyecto es un esfuerzo grupal. Asuma que los demás miembros de la comunidad también están trabajando en la misma dirección.
 
4. Los moderadores podrán eliminar su publicación o publicaciones si quedan  sujetas a discusión o  si existe en sus palabras cualquier señal de malas intenciones.
 
5. Si tiene algún problema con el equipo moderador o algún miembro oficial del equipo de desarrollo, deberá publicar con una actitud libre de intrigas ni acusaciones infundadas. Recuerde que los  desarrolladores no están allí sólo por usted.. Si no recibe pronta respuesta, pruebe a dividir la descripción del problema en partes más simples y vuelva a publicar su pregunta manteniendo  una actitud positiva.

6. Su propósito principal en este foro es ayudar a otros y hacer aportes constructivos. Si se determina que es un elementa netamente negativo para la comunidad, nos reservamos el derecho de eliminarle e incluso reportar las publicaciones a los moderadores de  bitcointalk.

7. No publique nada que engañe a los inversores. Revise su publicación antes de publicarla, ya que no podrá ser eliminada durante un lapso de 24 horas. Si no está seguro de algo, siéntase libre de preguntarle a alguien primero.

8. Sus publicaciones podrán ser eliminadas y podrá ser excluido de los Foros si tiene un historial de publicaciones ofensivas.

9. Después de 3 publicaciones ofensivas, sus publicaciones futuras y / o su cuenta pueden ser prohibidas a la sola discreción de uno de los administradores de nuestro foro.

7
We are offering the following bounties for these projects:

- Roadmap (Fork the roadmap into a Spanish version):
500,000 BBP

- New Coin Launch Thread (Spanish) - Fork the New Coin Launch thread into a Spanish Version
1.25MM BBP

- Whitepaper PDF (Spanish Version)
3.25MM BBP



8
September 2020 Release


Welcome to the Biblepay September 2020 Testnet Testing thread for POOS!


In this thread we will be testing:

- POOS (Proof of Orphan Sponsorship):
     Verify the Sanctuary Owner may Sponsor a Cameroon-One Orphan (by associating this Orphan with the Sanctuary public key)
     Verify the legacy POSE ban system still POSE bans a node for lack of service
     Verify the POOS ban system will increase the ban for non-paid orphan accounts
     Verify the POOS ban system will decrease the ban once the orphan is paid for
     Verify the sanctuary cannot revive itself unless they pay the amount owed first

- Coin-Age voting:
     Verify you can vote from the Proposals UI by right clicking a proposal and voting with coin-age
     Verify you can increase the default (configurable) coin-age percentage using the biblepaytest.conf key value
     Verify the voted tally shows the correct coin-age and distinct sum of users who voted
     Verify we can vote with coin age from the RPC

- ChainLocks and DIP0008:
     Verify that testnet LLMQ quorums are forming, and advancing
     Verify testnet LLMQ locked IX transactions occur automatically, and quickly (IE test autolocks)
     Verify chainlocks locks the block (getblock hash, verify when entire block is IX locked, then it is also chainlocked)

- APM (Automatic Price Mooning)
     Verify the subsidy is 7 if an APM decrease event occurs day-over-day
     Verify the subsidy is normal if the price is unchanged, or if the APM increase event occurs day-over-day

- DWS (Dynamic Whale Staking)
     Verify the 'dws' and 'dwsquote' commands work as dedicated commands.


Additional Testing for BiblePay Unchained - added on August 6th:
First, read this guide:
https://wiki.biblepay.org/Using_Unchained


- BIPFS (Biblepay IPFS)
     Test exec bipfs_file (Upload a file into unchained).  Once the file is uploaded, verify the price, the duration, the density, and that you can navigate to the URL.
          (Verify both large and small files).
     Test exec bipfs_folder (Upload a folder into unchained).  Verify the price, duration, density, and a few URLs from the upload.
     Test uploading an encrypted file, retrieving the encrypted file (with exec bipfs_get), and re-opening the encrypted file.  Test it with a bad password also.
     Test exec bipfs_get (Download a file).
     Verify the sidechain sync height (Info Sidechain Sync Blocks).
     Verify bipfs_list (the uploaded file is now in the sidechain).

- BIPFS C# Client
     Test file upload and folder upload in the c# client.  Verify the file density, duration, and URL result, and download the asset from the URL.
     Verify the charge amount and the TXID was charged to the payment source (via API-KEY method).
   
- DWS UI
     Verify you can make a DWS burn from Send Coins Entry (these burns are always 90 days).  Verify the Quote works.


- Verify Monthly Budget changes:
     Verify as of block 55720, the sanctuary payout is 8.75% higher and the monthly governance budget is 8.75% lower












NOTE:
Most likely you will need to recreate your sanctuary, unless you see your sanctuary is POSE banned.  In that case you can revive the sanctuary with 'exec revivesanc'.


Starting Version:    1.5.1.7+


(Please ensure your version is greater than this, otherwise your testnet branch will not sync. 

We are at block  ____52500_____ as of July 21st, 2020).

BlockHash:
getblock 52500   "hash": "12287aa66bb3e29c354b276aa1738efcf93ea031c8b57d9e17ea6242252604f1"



Testnet Download Links:


Ready:
     Windows 64-bit:      https://biblepay.org/biblepayevo64develop.exe
     MacOS QT: https://biblepay.org/biblepaycore-evo-testnet.dmg
     Linux 64 bits II (QT/biblepayd/biblepay-cli) zip:  https://biblepay.org/bbp-lin-develop-64.zip


To self compile:
https://github.com/biblepay/biblepay/blob/develop/BuildBiblePay.txt





CONFIGURING FOR TESTNET:


Create a biblepaytest.conf file with the following contents:
testnet=1
debug=1

Place the file in ~/.biblepay



Start testnet by typing:
./biblepay-qt -conf=biblepaytest.conf

(Note the blocks and chainstate will sync into the ./biblepay/testnet3 folder.


NOTE: This version will also work side-by-side our production nodes,
so, you also have the option if you are short on machines, to run TestNet side by side a prod node!

To run a TestNet Sanctuary:
https://forum.biblepay.org/index.php?topic=391.msg5968#msg5968

How to create a deterministic sanc from scratch:
https://docs.dash.org/en/stable/masternodes/dip3-upgrade.html

__________________________________________________________________________________________________________________________________________________________________________________________




9
Discussion and Suggestions / BIBLEPAY Wishlist
« on: July 15, 2020, 09:38:33 AM »
The purpose of this thread is to post features that you would like to request (or verify the possibility of creating) within:

BiblePay Core Wallet
Foundation.Biblepay.Org (Gospel or Pool features)
Mobile Wallet

Some examples:
A groundbreaking idea
A feature that another coin has (for example, a feature you found in the top 50 coins that we don't have)
A workflow process that would clearly provide value (example:  our Add a New Proposal page)
A gospel feature (such as our prayer request or video list etc).

Bugfix requests should still be entered as github issues here:
https://github.com/biblepay/biblepay/issues


10
Production Proposals / Should Sanctuaries fund our Orphans?
« on: July 01, 2020, 03:44:09 PM »
I am investigating the future scenario where we require each sanctuary to fund a single orphan in order to be a paid sanctuary.

This partially comes from the complaint that our Sanctuaries are only in name only (IE, why are they called sanctuaries -- if they are nothing more than masternodes -- and they dont do anything for us?).  Why do they sit and receive rewards for doing nothing?

(I was under the impression earlier in our launch, that we would create some type of workflow, and have sanctuaries perform something fundamental, such as entering expenses or liquidating orphan funds, but in reality we never did establish a workflow like that.  I argue that making a sanc responsible for one orphan may be the key to that self enforcing workflow).  A sanctuary could be a 'safe haven' for one child.
The sanctuary purpose is to sponsor a child, write letters back and forth (if possible), and provide due diligence for our other charity endeavors.

One disappointment I currently have with the sancutary ecosystem is these investors seem to be detached from our project (I feel as if Im the lone decision maker when I vote on issues).  I would personally rather see votes originating from people with 'skin in the game' and those same people are technically the ones who care about the children.


One other problem with our current sanctuary setup is we have 250 sancs that have to pay for hosting.  Id rather see 'sancs who sponsor orphans' pay for hosting.  In that model, you gain a lot of efficiency - meaning that we have less infrastructure overhead.  (If we really do intrinsically grow then yes we have more hosting but we also have more children being supported).

So of course the pro to this idea is those that sponsor orphans will be the ones who make sanctuary ROI.

The main downside to this idea is more investor friction (harder to do things like fractional sancs).  But I argue also, that this can be addressed quite easily by modifying our turnkey fractional service to include orphan sponsorship costs.

So let me summarize what this proposal would entail:

- Each sanctuary will be required to sponsor one cameroon-one orphan
- If a sanctuary locks coins and does not sponsor an orphan, they will eventually (over 24-72 hours) get POSE banned, meaning their payment income will stop.
- If a sanctuary is in good standing (IE they do sponsor an orphan) they will not get pose banned.
- Cameroon-one will be required to paste the masternode public key inside each sponsored child BIO (which is hosted by them).
- If the sanctuary masternode pubkey is not in the bio, this means the sanctuary will be POSE banned.  Or, if the sanctuary stops paying for the child, they will be POSE banned after they fall in arrears more than 30 days late.
- Cameroon-One will remove the public key from the BIO if the account is overdue by more than 30 days.
- The Sanctuary will link themself to an orphan by typing a command in the wallet. (Or cameroon-one will add new bios in the wallet by persisting new bio-ids with pubkeys).  Either way, this will give our sanctuaries insight into checking the pubkey-bio pair during each POSE round.
- Rob would modify the foundation web site to accommodate fractional sancs with orphans attached.  Another words, investing in a fractional sanc would need to have a reward component and a cost component (the sanctuary reward minus the cost of the orphan / 30).  This would give us an "inroad" to maintain fractional sanc investors.
- We will test to ensure no more than 50% of the network can be POSE banned at a given time (this is in case a disaster scenario occurs, where Cameroon One is down and the internet is down, this means our sancs will not pose ban more than half of the network).

As far as what this looks like for investors after this potentially goes live, I believe we would see the sanctuary count drop to 40 or so.
Then the ROI for a sanctuary would be astronomical (IE 500% per year) simply due to the lack of participation.
Making it very enticing to sponsor a child and have a sanctuary (at first).
Of course, if you plot this on a graph you would see a sweet spot (where ROI is 100% per year or so) where the sanctuary count would settle on (maybe 75 sancs?).

(I dont mind making a graph later and posting it to show the effect).
But the point is, this idea does appear to offer a high scalability effect for child sponsorships.
Meaning that if we remain small we will be paying for 40-50 children organically with a low sanc count, and if we grow, obviously we have the ability to sponsor 1000-2000 if we were to take off to half of the size of Dash (who has 4,500+ masternodes) or even 10% of the size of dash based on economics.








11
I ran across this project today while I was looking at clean water projects.
It struck me as cost effective for such a big impact (IE helping 200 people in a village per distinct well over a long period of time).

https://www.paaniproject.org/donate

Please check it out and let me know if there are any red flags.

Otherwise I propose that we donate two ($600) wells (for a total of $1200) to help 400 people get water.

I am seeking 6MM bbp for this project.  If there is any deficiency, I will cover the difference.

I will also donate at least one more well on top of the BBP funding (so we can do 3 wells with funding for 2).

EDIT:
We have 6.3MM in the foundation treasury.    I propose we use 6MM of those funds for this project.
I will still enter a sanctuary proposal, this way we can see if it gets upvoted first - but we will not need to use governance funds for this.)


EDIT 2:
It looks like we can have a well named after BIBLEPAY, and they will send us 20-30 pictures of the work!
https://closeup360.com/news/lakers-lebron-james-water-well-named-pakistan/


We will definitely request this!





12
Production Proposals / Vote on Future Currency Name II
« on: June 20, 2020, 10:08:12 AM »
First I would like to say that switching our currency name from BiblePay to DAC is in the spirit of growing the community and not blocking potential users who might view us as overly religious.  We are not doing this in any way because we are ashamed of the gospel; but instead to appeal to a broader cross section of the world first.

We can still keep the bible in the wallet, and spread the Gospel of Jesus in certain specific areas (such as the doctrine section of foundation.biblepay.org) if we re-brand.

Anyway, Jesus said the Gospel is for those who are sick and or in need (not for those who are already saved and sealed).

In our last vote, our community strongly gravitated towards re-branding in contrast to having dual brands.  One of the old questions was: Should we keep both biblepay and DEC, and the supermajority felt it was not a good idea to maintain two brands. 

The supermajority liked DAC more than DEC also (hence why I have more choices up above for variations of DAC).

In light of that, this vote attempts to hone in on the recommended currency name (and see if the idea is maintained).

There are 3 tiny coins with the ticker DAC already:  Davinci Coin and DACash (DAC) and DACC - Decentralized accessible content chain (DACC).  I think what we would do is hold a separate vote for the ticker.  We could possibly make the ticker XDAC  (none are taken like that) or DACBBP.     So for example:  We would be Digital Autonomous Currency (XDAC).

I prayed about this decision and I'm not receiving any negative response about switching from BIBLEPAY, but I don't want to influence the voters, so please vote.

Finally on the Charity vs Non-Charity debate, during the last vote more people voted for autonomous currency than autonomous charity.  This is another case of keeping ourselves generic (and not pegging us to the stigma that we spend all the investors money on charity or that the price will always go down because its all spent on aid etc). 

If anyone has a variation that is even better please post it and Ill consider adding it to the list.  We own dac.ngo, dac.ong, dec.app, and coin.ngo.  I kept coin out of this because I believe its just too generic compared to dac and dec.


13
Archived Proposals / Add new charity partner - SAI.NGO
« on: June 10, 2020, 05:30:46 PM »
I had four telephone calls with Stephen, president of SAI.NGO.

I explained our mission, and how we were seeking a cost effective orphan provider, potentially below $38 per month.

We have come to an agreement to sponsor orphans at a rate of $20.00 per month, who are orphans from the streets in Venezuela who lost both parents. 

The orphanage they stay at is primarily receiving more donations for animals and veterinarians than humans at this time.  The caretakers they have are sometimes only veterinarians, who are already receiving wages from SAI to care for animals.  In this agreement, they take in the orphan and our sponsorship allows SAI to buy local food (locally sourced flour, sugar, etc at local rates) and bring it in.  They are both government audited and guidestar certified.

We have received the first 10 orphan bios: (filter by SAI.NGO):
http://foundation.biblepay.org/SponsorOrphanList

Additionally we received help on this endeavor from Costa82, who actually lives in Venezuela and is going to do additional due diligence in this matter to ensure the beneficiares receive all of our gifts and will update us with any red flags.

SAI GUIDESTAR rating:
https://www.guidestar.org/profile/81-1747993

SAI website:

https://sai.ngo

I asked Steven for a study that their org has created for one of his large donors that proves the transactional chain between donation and beneficiary; they have one available in PDF format:

** Integrity & case studies provided by SAI **:

Animals:

https://sai.ngo/wp-content/uploads/2019/11/Animals-SAI-.pdf

Orphans:

https://sai.ngo/wp-content/uploads/2019/11/SAI-Brochure-1.pdf

https://sai.ngo/donor-advised-funds-donations-daf-venezuelan/





14
Archived Proposals / Approve Budget Changes
« on: April 30, 2020, 09:17:07 PM »
In the first month of RandomX mining (April 2020), we raised approx. 1.90 XMR.
Due to the success levels of RX, I propose the following changes to our reward structure for each heat mined block:

- Retire POOM as of June 2020 (remove listchildren, cancelsponsorship, sponsorchild)
- Free up the daily GSC budget spent for POOM (240K per day, 35% of the GSC budget)
- Allocate this 240K per day into the heat mining reward (raising the heat mined reward from 2400BBP to ~3500bbp)
- Do not increase the Sanctuary reward (instead maximize the RX reward)

Part II (DWS - Dynamic Whale Staking):

I feel that DWS was very successful, and it was grabbed relatively quickly - even with the last adjustment.  I feel it gives us a fighting chance to allow outsiders to buy up the SX free coins.

I propose these changes:
- Double the DWS available emission level, so more burns will be available
- Increase our deflation rate to pay for the new level
Specifically, we would change the GetAnnualDwsReward level from .325 to .64, then we would increase our deflation level in GetBlockSubsidy.


15
June 2020 Release


Welcome to the Biblepay June 2020 Testnet Testing thread.


In this thread we will be testing:


- 'exec price' : XMR price has been added
- Sanctuary Voting :
     (This is the ability for a sanctuary to vote on a spork, and if the Vote outcome is a PASS, the spork will go into effect.  If it is a FAIL we need to see this spork fail to enter into the chain).

- Anti-Censorship-Feature (ACF)  - Although I went through the pain of coding this, releasing it and testing it, I have decided that (as I believe we as a community) will be better off with BiblePay unchained for this use case (as it is safer and does not risk bloating the governance system and the nodes).  So for safetey reasons, I have removed this and now am planning on releasing the design for Unchained.  (This is a sidechain that holds documents off-chain).

- Removing "BiblePay-Evolution" from the windows wallet and fixing the default program directory name (it is still Evolution).  This should go back to BiblePay.  Check to see if the windows installer wizard is correct.

- Test a VendorList change (Charity monero addresses in a semicolon delimited list) and a PoolList change (allowable RX pools).

- Remove POOM from the wallet (remove poom listchildren, poom pay).  Move POOM payment budget from GSC to Heat mined blocks.  Ensure these heat payments go to the heat side and not to the sanctuary.  I believe POOM causes the GSC budget to drop by 240K per day, and the mined block subsidy to rise by 1200~, and the sanc payment should stay the same.

- Any Dash changes that occurred between Jan 1,2020 and March 30th?  Ask MIP?  MIP has made me aware we need a little more time to move up to .15, because Dash has changed 1800 files!  So lets shoot for releasing .15 in September.

- The ability for a RandomX hash to be mined in a more RX compatible way (check to see if foundation.biblepay can receive a blakehash as Solution #1) (This is just a reminder note that may result in a code change in the core wallet if this streamlines the xmrig code to be 100% compatible with the xmrig branch), Checking this.  (This basically frees us from maintaining a special version of xmrig).

->  Great news, I tested pure merge-mining using the plain vanilla xmrig, and it worked.  The changes are in this version already.

- Test Marcus Antonios Russian and Ukrainian Bible viewer(s)


Starting Version:    1.5.1.0+


(Please ensure your version is greater than this, otherwise your testnet branch will not sync. 

We are at block  ____37650_____ as of May 1st, 2020).

BlockHash 37650:
573935383afc18055f0207355e49262a4243db5705d019506aac153eba5c503e


Testnet Download Links:


Ready:
     Windows 64-bit:      https://biblepay.org/biblepayevo64develop.exe
     MacOS QT: https://biblepay.org/biblepaycore-evo-testnet.dmg

     Linux 64 bits II (QT/biblepayd/biblepay-cli) zip:  https://biblepay.org/bbp-lin-develop-64.zip


To self compile:
https://github.com/biblepay/biblepay/blob/develop/BuildBiblePay.txt


Retiring (do not use these downloads):
     Linux PC 64bits Daemon:     https://biblepay.org/biblepayd-evo-testnet-x86_64-pc-linux-gnu.tar.gz
     Linux 64 bits QT:       https://biblepay.org/biblepay-qt-evo-testnet-x86_64-pc-linux-gnu.tar.gz






CONFIGURING FOR TESTNET:


Create a biblepaytest.conf file with the following contents:
testnet=1
debug=1

Place the file in ~/.biblepay



Start testnet by typing:
./biblepay-qt -conf=biblepaytest.conf

(Note the blocks and chainstate will sync into the ./biblepay/testnet3 folder.


NOTE: This version will also work side-by-side our production nodes,
so, you also have the option if you are short on machines, to run TestNet side by side a prod node!

To run a TestNet Sanctuary:
https://forum.biblepay.org/index.php?topic=391.msg5968#msg5968

How to create a deterministic sanc from scratch:
https://docs.dash.org/en/stable/masternodes/dip3-upgrade.html

__________________________________________________________________________________________________________________________________________________________________________________________






Pages: [1] 2 3 4 5 6 7 8