136
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.
137
Archived Proposals / Re: explorer.biblepay.org Server September
« on: September 08, 2018, 02:13:09 AM »
You also have a nice 4 core / 14GB for 12€ ($13.89) at Contabo
https://contabo.com/?show=vps
I have a 2 core vps for a BTC/LND node and no issues so far.
https://contabo.com/?show=vps
I have a 2 core vps for a BTC/LND node and no issues so far.
138
TestNet Discussion Archive / Re: TestNet Testing Thread - Test IPFS Integration (Decentralized IP File System)
« on: August 28, 2018, 04:25:04 PM »139
TestNet Discussion Archive / Re: iOS MOBILE WALLET - BETA TESTING
« on: July 31, 2018, 03:22:36 AM »BiblePay Foundation might be "Publisher" in the future?
Legal Formation of The BiblePay Foundation
https://forum.biblepay.org/index.php?topic=215.0
Yes, that could be a good idea. We would need to purchase a full apple dev enterprise license instead an individual one, but we would have that part covered and would also be entitled for private app distributions.
140
TestNet Discussion Archive / Re: iOS MOBILE WALLET - BETA TESTING
« on: July 24, 2018, 04:38:20 PM »When I try to send BBP I'm getting:
Error
Network Fee conditions are being
downloaded. Please try again.
Is the IOS beta wallet still operational?
It's stopped at this moment. I can't upload new versions because Apple don't approve them. It seems that they require that the publisher has the same name as the coin, to avoid "copyright" issues.
We will try to make some workaround whenever possible.
141
Archived Proposals / Re: Legal Formation of The BiblePay Foundation
« on: July 24, 2018, 04:35:32 PM »
This is going to be a landmark decision for Biblepay, thanks Rob for your work defining the process and the Foundation.
142
Archived Proposals / VMWare Fusion license for MacOS testing
« on: July 05, 2018, 02:07:59 AM »
Hi,
I found this really useful tool, that allowed us to test the MacOS version of the Biblepay QT wallet.
As you may know, testing the DMG in the development Mac was misleading, because a dev Mac has all the libraries installed and it's impossible to know if you are leaving one or the other behind.
Moreover, Apple compiler links dynamically by default, so you are forced to whether force a static link (I could do that with libboost, libcrypto, etc.) or include and codesign all the dylibs into the bundle (this was the case for QT framework libs).
I could not have made it without being able to create an empty MacOS 10.13 (High Sierra) virtual machine. Also, this tool allowed me to test in previous OS version, 10.12 (Sierra), creating another empty VM. This way I could check that the DMG bundled all the required binaries.
I am using the 30-day evaluation version, but I would need to get a permanent license to keep on testing on the future (and future MacOS versions that are coming).
Cost is 88,95€ ($104) @$0.00185107/BBP = 56184 BBP requested
Thank you for your time.
I found this really useful tool, that allowed us to test the MacOS version of the Biblepay QT wallet.
As you may know, testing the DMG in the development Mac was misleading, because a dev Mac has all the libraries installed and it's impossible to know if you are leaving one or the other behind.
Moreover, Apple compiler links dynamically by default, so you are forced to whether force a static link (I could do that with libboost, libcrypto, etc.) or include and codesign all the dylibs into the bundle (this was the case for QT framework libs).
I could not have made it without being able to create an empty MacOS 10.13 (High Sierra) virtual machine. Also, this tool allowed me to test in previous OS version, 10.12 (Sierra), creating another empty VM. This way I could check that the DMG bundled all the required binaries.
I am using the 30-day evaluation version, but I would need to get a permanent license to keep on testing on the future (and future MacOS versions that are coming).
Cost is 88,95€ ($104) @$0.00185107/BBP = 56184 BBP requested
Thank you for your time.
143
TestNet Discussion Archive / Re: iOS MOBILE WALLET - BETA TESTING
« on: June 13, 2018, 08:46:05 AM »Okay... So that basically means that BiblePay would have to be incorporated (I don't know if this is the correct term) before we can publish the wallet for Apple?
Well... Plans are underway to achieve this, but I guess you could call those plans mid-term, so it would be really unfortunate if we could not publish now with an 'individual' account...
I can also incorporate my dev activity into a company but in Spain regulation is so suffocating that it's barely worth it. No wonder why this country's economy is degradating every month. You have to work for gobernment 6-7 months out of 12 because of the taxes everywhere.
144
TestNet Discussion Archive / Re: iOS MOBILE WALLET - BETA TESTING
« on: June 13, 2018, 02:02:46 AM »
I'm getting extra questions from Apple about the coin, and it seems the new Apple policy has hardened the conditions.
They now say that wallets are allowed but they need to be published under a "Corporate" account (now I only have a "Individual" account).
We can try it but... it's going to be difficult I'm afraid.
They now say that wallets are allowed but they need to be published under a "Corporate" account (now I only have a "Individual" account).
We can try it but... it's going to be difficult I'm afraid.
145
TestNet Discussion Archive / Re: Testnet June 2018 Mandatory Upgrade Testing Thread
« on: June 12, 2018, 03:09:02 AM »
So do we need 1.1.2.5 on both Sanc and windows controller wallet or just in Sanc?
Edit: ok I read again and it's about testing on a hot wallet Sanc.
Edit: ok I read again and it's about testing on a hot wallet Sanc.
146
TestNet Discussion Archive / Re: iOS MOBILE WALLET - BETA TESTING
« on: June 11, 2018, 04:59:54 AM »I do not have the Breadwallet Bitcoin Wallet installed.
Ok just to discard some conflicts.
I posted new beta to Apple but this time they rejected the binary and send me the classical questions about the coin. It will probably take 1-2 days to get response (and approval)
I discovered that Apple guys on Testflight approval near weekends are more picky than the ones on Mon-Thu shift.
I would use this as a hint on how to submit the app for final approval on App Store.
What's your opinion?
147
TestNet Discussion Archive / Re: iOS MOBILE WALLET - BETA TESTING
« on: June 08, 2018, 04:59:47 AM »The app is crashing when I try to open it. It crashed 4 times then opened. I have Touch ID on. I canceled it and manually inputted my password then it worked.
I can see some crash traces related to a problem in iOS queues I discovered yesterday. Not 100% sure that this is causing your crashes but there is a reasonable chance they are.
I will post now an update to address this problem, you will all get notified by Apple when it's approved and available.
BTW: do you have the original Breadwallet Bitcoin Wallet also installed in your iPhone?
148
Archived Proposals / Re: MacOS compiles - iOS version support machine
« on: June 08, 2018, 04:42:13 AM »
Finally part 2 was also solved.
I had to create and sign the executable into a MacOS bundle which was sort of complicated stuff (docs only refer to XCode IDE projects) and there is little or none info on manual bundling.
So we will have the MacOS wallet DMG uploaded to biblepay.org shortly.
I had to create and sign the executable into a MacOS bundle which was sort of complicated stuff (docs only refer to XCode IDE projects) and there is little or none info on manual bundling.
So we will have the MacOS wallet DMG uploaded to biblepay.org shortly.
149
TestNet Discussion Archive / Re: iOS MOBILE WALLET - BETA TESTING
« on: June 06, 2018, 04:59:50 AM »Does MEMO actually get captured in blockchain, or just the iOS app? You think it should be captured in blockchain? Maybe too much work right?
Currently it's only stored as metadata in the app database. Sending it to the blockchain would require to add an unspendable output. It increases size and fees, and it's not recommended behavior as it's seen as bloating the chain.
Quote
Other feedback:
- Send BBP > Scan . Only camera is possible. What I want to send someone BBP from a web site I went to. QR code is there, but how do I scan? This assumes I need a computer display or print it out, etc... If I take a screenshot on iOS, a way to import a picture would be good too, right?
usually you are also offered a text address along the QR, so you just have to copy and paste it.
Quote
- knowing who send you payment (BBP address). Someone send me 5 BBP and it was very difficult to send 1 BBP back as a test
it should show in the transaction detail popup.
Quote
- Address Book to send payment.
Address reutilization is worst practice towards privacy.
Quote
- Maybe quick access to explorer based on from or to BBP address - like %s you find in BBP QT wallet (right click go to explorer)
Would be ok, we have URL to explorer for UTXO recovery. I will note that one.
Quote
BOINC for iOS? That would be amazing, but I didn't think this is possible currently.
It's possible, I'm even preparing that feature for Android now. I must test the burn tx and implement some convoluted logic it has inside for banked/non-banked but there is no technical stopper.
150
Archived Proposals / Re: MacOS compiles - iOS version support machine
« on: June 05, 2018, 01:57:58 PM »
Ok so this was it:
It seems that, unlike Linux, MacOS has a predefined stack size, which is 8MB for main thread, and a pityful 512KB for the other threads.
This is the reason why biblepayd loaded the verses fine, because it lives in main thread.
But QT version launches it's own thread for windowing and when it tries to load the verses, it hits the 512KB limit for the stack.
Solution: I had to patch qthread_unix.cpp from QT 5.11.0 to increase the stack size of threads, compile QT all over again (317 minutes lol) and then... it worked!!!
So we have part 1 finished.
Now I'l begin part 2, creating and signing DMG file for distribution.
It seems that, unlike Linux, MacOS has a predefined stack size, which is 8MB for main thread, and a pityful 512KB for the other threads.
This is the reason why biblepayd loaded the verses fine, because it lives in main thread.
But QT version launches it's own thread for windowing and when it tries to load the verses, it hits the 512KB limit for the stack.
Solution: I had to patch qthread_unix.cpp from QT 5.11.0 to increase the stack size of threads, compile QT all over again (317 minutes lol) and then... it worked!!!
So we have part 1 finished.
Now I'l begin part 2, creating and signing DMG file for distribution.