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

Pages: [1] 2 3 4 5 6 7 8 ... 12
1
Rob, I am more concerned about the immediate than the future state.  My wallet has been down for three days now and nothing seems to be bringing it back up.  I am not alone in this, there are others in the same boat.  How do we get our systems working again?

Download the latest wallet version (1.2.0.1) and resync. That worked for me on several nodes.

2

I support you on this.


Are you able to publish to Apple Store at all? Would it say MIP on it instead of BiblePay?

I can't publish on app store (It would show up with my real name lol, not MIP), in fact to some point they even stopped me from publishing betas in TestFlight, so I can only publish to my own devices (internal test),

They state that only a publisher with name "Biblepay" is entitled to publish a wallet for "Biblepay", which is a bit silly because there is no company called "Bitcoin", "Bitcoin Cash" or "Ethereum" and many 3rd party companies are publishing wallets for them.

So my fear is that even if we create a "Biblepay" company, they take it to the next level saying that they don't publish wallets of smaller or not known cryptos. But in that case we have the option to publish wallets privately (this also comes with a corporate Apple license) which is what some companies like Binance are doing.


3
Production Proposals / [MIP] Feb 2019 compensation
« on: March 11, 2019, 05:09:05 am »
Hi all

I would like to kindly ask some compensation for Feb 2019 support/development tasks

MacOS and Ubuntu PPAs maintenance: 5h
Core Client - PoG engine interface development: 15h

In all, 20h or $800 = 4,047,559 BBP

I'll cap it to 1,000,000 (1M) BBP

Thank you very much

4
Hi,

I purchased a 1-year individual dev licence from Apple on April 2018 in order to have certificates for publishing signed DMGs for the Biblepay Core Client in MacOS, and also to be able to prepare a iOS mobile wallet to publish in App Store.

As you probably know already, Apple refused to publish such application because they don't allow it for individual accounts.

Currently our only alternative to create a iOS app is to acquire an Enterprise Dev license from Apple (priced 299€), which requires to consolidate a company and have a DUNS number. At this moment this is not available so we stuck here.

I want to request 99€  to renew the individual license for 2019 so we can keep our certificates to publish the Biblepay Core Client in DMG for MacOS.

At current prices (BTC@3464€ and BBP=5 sat) that would mean 571594 BBP.

Thank you for your time.

5
For me the decomission of PoDC is a painful but necessary step, at least if we aim to reach a much bigger audience.

If it has to be this way, it's probably much better do it now rather than in the middle of a new cripto summer (and risk losing that momentum).

I also see as an advantage the increase of PoW role back to a 20% of the mining rewards, I think it will help strengthen the network more than with what we have now.

6
Archived Proposals / [MIP] Jan 2019 compensation
« on: February 27, 2019, 08:40:03 am »
Hi all

I would like to kindly ask some compensation for Jan 2019 support/development tasks

MacOS and Ubuntu PPAs maintenance: 5h
Dash rebase (adding PoG code): 8h
Android app: 6h
 - rebuild with a previous NDK for compatibility with older armeabi devices
 - remove SMS_SEND permission for new Google Play policy compliance.
 - publish upgrade into Google Store

In all, 19h or $760 = 2783000 BBP

I'll cap it to 1000000 BBP

Thank you very much

7
BiblePay discussion / Re: Economical model thoughts and current state
« on: February 26, 2019, 04:37:36 am »
There are many fronts and not-so-many resources.

On one side, we would like to keep the fight on the "use as a crypto" monetary case by adding all latest Dash improvements, and try to keep up with them.
On the other side, Rob has been, and will keep on working on additional practical use cases, like IPFS and the Stratis port proofs of concept. While results might take a while to show up, I am pretty sure that we will be able to deliver something interesting.

8
Pre-Proposal Discussion / Tipping bot on Discord
« on: February 18, 2019, 05:34:01 am »
Someone is proposing us a tipping bot on discord

"the fee of my service  is only $30 good  for 3 months. included the maintenance if the tip bot
if you would like the live testing of the tipbot i made , just tell me if u like"

Sample screenshot


What do you think?

9
Pre-Proposal Discussion / Listing on pecuniaplatform.io (no fees)
« on: February 04, 2019, 02:16:58 am »
I got this through discord:

Quote
Hello
We can list biblepay. On https://pecuniaplatform.io/
This would cost you nothing we don’t have a listing fee
This would increase your exposure and offer your community a one-click service at a very convenient prices 1.99$/mo
We also offer you to show your banner during installation this give you access to over 50 new crypto masternode holders every day a targeted advertising
Only requirement is to announce the listing on your discord and retweet our announcement about biblepay listing
Thanks

As there is no listing fee we can go ahead and give exposure.
But we need to announce in Discord and Tweeter

What do you think?

10
Active Discussions / Re: Testnet - Test Proof of Giving
« on: January 22, 2019, 04:10:05 am »
1.1.8.3-Mandatory Upgrade for TestNet


- Highlight user in POG leaderboard UI
- Fix bug in POG block checker (IE compare rounded amounts) before
failing a block
- Add POG Leaderboard to toolbar menu

** Note:  Please upgrade as this version hangs up on old clients **

MacOS testnet version ready and Ubuntu testnet PPAs building now

11
Active Discussions / Re: Testnet - Test Proof of Giving
« on: January 12, 2019, 02:32:49 am »

On the DIP002, I agree on doing this on a longer term scale - for "best practices".

Completely agree on this. We will have enough  "fun" even making a workable devnet on the first approach so this would go on a later stage.

12
Active Discussions / Re: Testnet - Test Proof of Giving
« on: January 11, 2019, 10:28:10 am »
I think you can (given your availability) port the GetTitheParams function(s) (just the math function(s) like quantize, not the UpdatePogPool stuff) into the mobile wallet, and call the Pool API for the pindexBestHeader->chainTip() POG difficulty level (IE 0-65535) (only because the pindex during sync wont have your current diff since the blocks arent stored but instead computed in the large client), once you have that int you can then call for the GetTitheParams, and that gives you the 3 things we can quote the user (age, max, min).

I see this clear, POG diff level must be retrieved from sowhere else.

The POG transaction does not require, but we should, transmit the <nickname> XML and the <tither> address in the ".sTxOutMessage" field - I dont know if you have implemented that field in the mobile client yet, would that be hard to add that field to the broadcasted transaction?  Then you would need to ask them for their nickname somehow during setup (not sure if there is a config in there).  It actually is OK to skip those two as users will receive POG payment rewards back to the sending address but I still recommend us going the extra mile to add the ability to send the message, because it is frowned upon to send rewards back to the change address (in addition a lot of clients try to anonymize the change address, and also it creates more spam, IE mobile user jumping around in the pog pool with many addresses etc).

sTxOutMessage is already supported as it's part of TxOut structure (otherwise mobile app outcoing txs would not be accepted by the network once broadcasted). So far the string goes blank but I don't think there will be any problem to send nickname (once configured by the user) and other data.

BTW on a more long-term discussion, Dash-rebased version we will probably have to move all this sTxOutMessage dependant behaviour into "special transactions" infrastructure provided by DIP002 (which is conceptually the same but using the "payload" concept instead sTxOutMessage).

At this point, the tithe should be accepted in the pogpool, so I think it should be doable....  Of course we should talk more about our apple situation as what is the use in doing all this if we cant even get listed in the Apple store.

Well it could be available on Android version... and even if we can't get listed on App Store we could someday provide the iOS app as downloadable like Binance does (if we ever obtain an enterprise dev license)

13
Active Discussions / Re: Testnet - Test Proof of Giving
« on: January 11, 2019, 02:27:09 am »
MIP-

I wanted to make a small record of this so we dont forget - POG should theoretically allow us to help the unbanked - I believe all we need is the current POG difficulty level, a 'pog tithe' button, and the ability for the mobile wallet to send a tithe.  At that point, the user should enter the pog pool.

Ok noted. As long as tithing does not require to have full blockchain data loaded, it is possible to implement. Remember that mobile wallet only stores block headers and your own wallet's UTXOs and TXs.

14
Active Discussions / Re: Testnet - Test Proof of Giving
« on: January 09, 2019, 03:00:55 am »
Did you get your nickname working btw?

Only if  I pass it through command line, not config file. Same happens in Mac, I can try debug it when I find a moment.

BTW, the chat menu is not visible in MacOS, probably because the "About" menu role in QMenu has a special meaning in MacOS GUI (that moves the "about" menu options to the top-left position, besides the system "apple" menu option).

The only way for it to work ok is commenting both lines in src/qt/bitcoingui.cpp

ln 438 // openChatGeneralAction->setMenuRole(QAction::AboutRole);
ln 443 //  openChatPMAction->setMenuRole(QAction::AboutRole);

This way it shows fine as in Win version.

15
Active Discussions / Re: Testnet - Test Proof of Giving
« on: January 08, 2019, 03:33:19 am »
I launched 1.1.7.9 and resynced and all my previously mined coins in the last week dissapeared. Is this the expected behaviour?
Can someone post current block hash to check if I'm in the right chain? Thanks

Sunk818, MacOS testnet version is ready. 

Testnet PPAs are also building as we speak.

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