all usa companies is shit/crap/scat in EU we have LW,OVH,CONTABO,HETZNER,FORPSI etc ..... pls stop using USA crap/idiots companies pls USA=shit/crap  najvacsie totalne hovna su iba stade,iba kokutek staby vultr pomenuje masinu s 2jadrami 2CPU a nei 2cores this movie is about all TEXAS https://www.imdb.com/title/tt7349662/?ref_=nv_sr_1BlacKkKlansman Slovakia, please watch your language and be respectful or we will have to start deleting posts. Thank you. |
|
|
|
its so hard to pay professional youtuber guy which make video toturial?  SVK Noko your step by step guideline is wrong or? have we contact to this guy? https://biblepaywallet.github.io/ all his axx is inactive, thanks Noted, will review with Rob. What's axx? And what guide is SVK Noko working on? SVK_NOKO worked long time on Telegram: helped more new users started airdrop and mining with podc+pow axx= accounts Yes, thanks for the help on Telegram. I'll ask Rob if he has a contact method with the paper wallet maker. |
|
|
|
its so hard to pay professional youtuber guy which make video toturial? SVK Noko your step by step guideline is wrong or? have we contact to this guy? https://biblepaywallet.github.io/ all his axx is inactive, thanks Noted, will review with Rob. What's axx? And what guide is SVK Noko working on? |
|
|
|
My road to BiblePay (a year ago) started by googling "Christian cryptocurrency".
Regardless of which community forum-platform we use, SEO is extremely important and needs to be a significant part of our PR budget/efforts.
Noted, the suggestion will be on the weekly review list that Rob will look at. |
|
|
|
What does everyone think about the usability of BiblePay so far in the real world? And also the upcoming possible changes?
Dash codebase is heading towards in-chain user registration for easier payments. As we plan to rebase with their codebase, we will be able to offer the same features for our users, donors, churches and investors among others. This was also pioneered by Rob with the contact card feature but it's likely that we move it to the in-chain system to keep compatibility for future rebases. https://blog.dash.org/introducing-blockchain-users-428d87a1e87a That's a cool feature! How's the re-base going? |
|
|
|
What does everyone think about the usability of BiblePay so far in the real world? And also the upcoming possible changes?
Which changes are we looking at, the roadmap goals? https://wiki.biblepay.org/RoadmapMobile Phone Wallet
MIPs iPhone and Android Wallet (Both iPhone and Android are complete - Android deployed to Prod - iPhone waiting for Apple to approve deployment)
November 30th, 2018
90%
---
Marketing Campaigns Phase 2
(Proposal for PR Campaign, Language Translations)
March 31st, 2019
3%
---
BiblePay IPFS Integration and feature set
BiblePay adds the ability to store IPFS documents, business objects, and provide a decentralized DNS system for accessing file resources.
March 31st, 2019
5%
---
BiblePay Evolution (Dash) Rebase
BiblePay merges and releases all of the Evolution codebase - and re-launches as BiblePay Evolution with a PR campaign and with a BANG! June 30th, 2019
5%
---
Market Biblepay as a Utility
BiblePay is working on an IPFS revenue stream derived from leasing fees generated by storing documents in IPFS hosted with BiblePay.
This cements BiblePay as a Utility.
December 25th, 2019
0%
---
Biblepay Debit Card
Partnership with VISA/MasterCard/or Generic Branded Debit Card
December 25th, 2019
1%
---
E-Commerce Integration
Integration with Retailers accepting Biblepay plug-in
December 25th, 2020
25% Yeah, and Rob's November announcement. |
|
|
|
|
What does everyone think about the usability of BiblePay so far in the real world? And also the upcoming possible changes?
|
|
|
|
Is there a problem with the main pool right now? It seems to me that it always shows the same information for hours now and it also hasn't found a single block today.
P. S.: Thank you thesnat and tmike for stepping up and doing great work which cannot be appreciated enough! Reading through the last couple of days of this thread really brings up hope again for this coin. God bless your community work and the work of all the devs!
Thanks dave. And we are open to any suggestions as well as any help you can provide. |
|
|
|
Parallel Paths for BiblePay - Future IT and RoadmapBy: Rob Andrews - Founder We learned a lot in 2018 that was not readily apparent during launch, and as in all businesses, we need to make adjustments in order to be viable. Our core vision is not changing: We still benefit orphans by giving 10% of our monthly emission, we are partially green on our mining side (our cancer miners are doing valuable work), we are CPU based - therefore anyone can mine us, we are Christian at our core - but appeal to everyone as a utility, we are deflationary and appeal to conscious investors who would like to see a more Christian investment, we have an intelligent team capable of taking us to our destination, we spread the gospel through the blockchain, and we innovate new gospel features. However, with the rapid pace of changes in this space, it is understandable we need to make some changes unless we wish to stagnate. One major change to our roadmap is our official position on Stratis. Although we still stand behind stratis and their core mission, and wish to remain informed and align ourselves with the potential value in the stratis codebase, many factors influence using stratis-c# as the primary production platform. The considerations being evaluated include: The latest bitcoin security commits, segwit, BLS and BLS secret-sharing, Dash's evolution commits, the lightning network, on chain storage, etc. In general, I want to first give kudos to the main devs of stratis. They are doing something almost impossible in order to get stratis to be compatible with the latest bitcoin version. Where we have to make our decision however, is weighing the benefits of the most cutting edge - to be released features in bitcoin and dash. Biblepay has discovered that it needs certain boilerplate abilities, and, pending IPFS integration, maps to IPFS, Segwit and potentially some of the latest Dash features (for reasons explained later). Additionally, there are over 100 features that have been added to bitcoin and dash-QT, that the existing features users have become very accustomed to (for example coin control), the HD wallets supporting features, etc. In light of this, I will be recommending that we adjust our roadmap to move stratis to 'R&D (research and development)' for future consideration and integration, but we move the Dash rebase to our more short term priorities. The goal is for us to do the due diligence on rebasing biblepay to have the latest dash features, so that we can leverage some of the latest features to store our IPFS relationship in a more resilient manner (IE our business objects). In summary, this means pushing Stratis out to 2022 and considering it an R&D project, and moving Dash Rebase to June 2019. Also relying on Dash's release as our PR event to be released with any other large BBP feature that is worthy of a giant PR event. Changes for IPFS:IPFS allows BiblePay to store files on our own network in a decentralized way. To use IPFS efficiently, we need to become a private IPFS network. This requires two additional features to be added to our core (private swarming and leased-pinning). NOTE: R&D test cases have proven IPFS can run in its own private network with a BiblePay swarm key, can auto-pin successfully, and IPFS mining can be made provable with range requests. Reasons for IPFS:There are many very useful reasons biblepay would want IPFS: Allows us to store business objects (think letters, expenses, revenue, contacts, object-votes, gospel-links, Christian-video-uploads, etc). Realize that storing business objects gives BiblePay a revenue stream. A revenue stream cements BiblePay as a utility - and that is important over the long term so that we always pass the Howey test. Passing the Howey test allows us to be listed on the largest most credible exchanges. It also shields us from legal damage, and allows us to partner with the most credible partners. Reasons IPFS cannot be at the Sanctuary level:There are very important reasons to first explain that Sanctuary investments are important for BiblePay's sustainability (investors buy sancs for ROI, and that allows us to fund our orphan operations). However, the harder we make biblepay to setup sancs, the harder it is for an investor to gain access to the investment. Therefore, to continue to be compatible with turnkey masternode services such as GIN and Apollon, we must not force hard requirements on sancs, such as requiring them to host IPFS files. If we do require a sanc to host a public IPFS node (with firewall requirements, public data sharing) we also risk a model that penalizes sanc payments when some 'investor' sancs do not perform. Therefore it is recommended to leave Sanctuaries as they are; not hosting IPFS files. Reasons IPFS should be at the mining level:So that we can offer turnkey Sanctuaries, we may offer IPFS mining. The concept of a content economy: The content economy is a concept Rob is considering for BiblePay. This is an environment where the user becomes more of a Christian community member. In this model, users are rewarded in BBP for doing important tasks, such as watching a Christian video upload and voting on it. (The users UTXO weight in the vote would drive the net vote weight, as the assumption is those with more weight hold more voting power). Consider that one with low weight could otherwise destroy the credibility of the poll-object. In this model, Christians find worthy youtube videos that edify other users, and upload the video in the 'Christian Video upload page'. Most of the rewards would be paid by distinct UTXO weight to the voters. This would reward those that spend the time in evaluating items with the actual rewards. (We will need to discuss giving the ability to cite bad votes from one community member to another, such as : Report Voter - with enough votes against a member we may consider adjusting a voters reputation score). Outgoing orphan letters may also be voted in the same way (IE in general, any object marked as votable will have a voting list available, and apt for rewards). Pay-to-preach sermons can be recorded by a community member and uploaded as a Christian video. The video would be voted in an identical way as other Christian video uploads. Rob is working on testing an opensource video upload tool to be integrated in that will automatically convert a youtube video into an IPFS document upload. One of the goals of the content-economy is to make BiblePay a platform that appeals to Christians so they feel comfortable to come back and actually check it for new content.I envision making BiblePay into a useful platform, one in which Christian's feel compelled to regularly use.One of the use cases I envision is having members pick a very edifying subject, such as Rapture, and uploading Christian videos only on Rapture for the Rapture area. Then, those interested in Rapture log in every day and follow the Rapture area, etc. Other areas such as end-time-visions, can be created etc. To have PODC or No-PODC:Realize, that IPFS mining will only affect the heat miners. IPFS mining modifies POBH to be IPFS-POBH mining, a greener blend - and PODC still exists in this scenario and plays well with IPFS. However, one concept we will be discussing in a new dedicated forum thread is the viability of POOM (proof of orphan mining). This is only a concept, and could potentially replace PODC. The core of the concept is re-directing the electric costs used for PODC into personal monthly orphan sponsorships. And creating a sanctuary review process to individually approve each individual orphan receipt (with a governance vote good for 30 days). In this scenario, we trade the PODC electric expenses for monthly orphan sponsorships, which could be very valuable for our community - since it is estimated that we could sponsor over 1000 monthly orphans with the equiv. electric savings. (POOM is also interesting in the sense that it solves our centralized fiat-liquidation vendor payment risk issue(s)). What are the devs working on:- Bhavani: Governance bar chart with totals by expense type for BiblePay-QT. An HTML map with pins displaying Christian camps.
- MIP: Church tithing in-wallet. Evaluating the entire dash commit history and making diffs with BiblePay.
- Rob: IPFS range-requests and an IPFS miner. Orphan outbound letter writing page in BiblePay-QT.
Additional updates:- MIP now has full github access as our second dev
- Compassion letters have been mailed to the translators (59 letters this month)
- The one prayer someone accused us of deleting was an accident (about 20~ days ago)
- forum.biblepay.org ownership has transferred to Thesnat21, some structure changes have been implemented.
|
|
|
|
2. I added a new miner. He is getting rewards already. Of course his CPID is synchronized with wallet. But lets take a look what shows https://biblepay-central.org/en/podc/user/2024825/It shows: No CPID - wrong, he has already No Address - wrong, he has one No next payment - wrong, pool.biblepay.org shows next payment No podcupdates - not accessible No history - wrong, he already got a payment Websites which are not up to date are throwing bad light on BBP. I wrote this here many times. Solution: keep BBP official (there is a link from biblepay.org) websites up to date or cancel them completely I think that was a quality site but for some reason it is not maintained anymore. I will talk to the owner and see what's going on. If it continues to be that way I will suggest it be removed from the main BiblePay website. |
|
|
|
Thinking out loud ....
I don't think the timing is as big an issue as the confirmation things are working ok..
I'm thinking a web page/service, compares data in semi-real time and gives you a status report.
Thoughts? Would you use this, and/or would it help adoption?
Yeah I think that would be a great idea before the whole process is streamlined. |
|
|
|
Regarding new perspective miners.
Start mining BBP is still hard work. It takes 3 days net time for experienced BBP person to configure it and get first reward. There are big waiting times for CPID synchronization, pool.biblepay.org RAC synchronization and so on. I started in friday morning, without any problem and first reward I will get in tuesday. I haven't lost a minute but because of waiting times it takes 3 days, maybe 4.
What can I say.
Minority from new miners will withstand with this and end this process succesfully. There will be no network growth with rigid system like this. It needs much more simlicity for new miners get in.
I will let the devs know this and see if we have any plans to make mining easier. Thanks for the suggestion. |
|
|
|
** Improving BiblePay's Image **
I think we have outgrown our original communication model in this forum. When I come in and view the posts after a good night's sleep, I see a certain level of negativity that has crept in, and is persistent frankly, and its shameful for a Christian Community (or ones that represent Christ) to be so full of disagreements, arguments, spying, attempting to hurt others, etc. I feel that these elements of attempting to prove one another wrong, discover secret information (IE voting, how many nodes ones owns), proving others are "right" about things - these are rooted in insecurity and also threaten the security of others. I've come to the point where I disagree with a critical threshhold of information on this forum. Some people don't have the morals standards and ethics to hold back negative feelings about others.
I'm not standing here as one who isn't willing to set an example. I am willing to completely forgive and treat everyone here anew, and set a good precedent going forward. So please don't reply and say, look at you, you are the one who started all this - wait - Let's not blame others - lets not judge - lets not hold grudges - lets start over.
This forum is sapping energy from our creative side and our productive side. It's not a net positive anymore. Things have to change.
Therefore I am going to take TheSnat's advice, and recruit a "Community Manager". A liaison between developers and the forum.
The Community Manager will gather both compliments and complaints, gather IT requirements, and other items that are relevant and create a weekly report (and sometimes in an ad-hoc fashion more frequently for mission critical problems such as production support issues) and forward these to our developer address (which I will create).
The dev team or myself will create a regular weekly reply with answers to the issues, and optionally will answer some in an adhoc-fashion - especially where they are mission critical.
Please discuss who wants to represent the BiblePay community as Community Manager and if you need support from me, please send me a PM if you need a poll created on the forum with the shortlist of candidates.
Any volunteers? I also suggest maybe have 1 or 2 people instead of just one. Not sure if the person will be paid for this so splitting up the workload may be better. What I mean by being paid is we don't have that much resource right now. |
|
|
|
|
Zthomas, like what you said.
|
|
|
|
Reposting here since Rob deleted my post. *** HUGE CHANGES IN BIBLEPAY TO IMPROVE OUR COMMUNITY AND HELP OUR CREDIBILITY AND CREATE STRENGTH ***
So this all started when one of our fast participants, Andy from LA offered to help with a few things. Things that resonated with me because we both pray for BiblePay and receive confirmations about issues.
Who is Andy and who are the fast participants? This makes me feel like the rest of us aren't important to this project at all.
Key Man Risk: This started with a conversation from one of Andys clients, wanting to get into BiblePay as a whale, but he was afraid that I was the single point of failure. After showing him the DAO page, many, many changes were put into play. One being that we are working on an internal plan to remove key-man risk in Phase 1 (that is at the end of this month). More info will be given on this today. This will eliminate key-man risk.
This was a problem we have been discussing for a while now but who will also have the keys? Are the changes really going to decentralize BiblePay?
Sanctuary Simplicity: The whale would not join unless they find a way for a one-click masternode. In this case, MIP is now creating a script for one-click sanctuaries. We also reached out to GIN who came through for us for decentralized sancs.
That's great but how many percentage votes is this person going to have?
The problems with the BiblePay foundation are that we were becoming centralized, and "ruled" by only 6 individuals, with governmental systemic risk. This gave the rest of the community the feeling that their masternode investment voting rights were not being used appropriately by biblepay, the biblepay directors were "better" than everyone else (IE could make legal decisions and trample on the rights of the community). Arguably, one of the most important issues raised was the governmental risk involved with a centralized foundation. This was the risk of being a lightning rod for a government to shut down biblepay or force biblepay to add wallet rules that remove anonymity.
Who is complaining? I have heard of no complaints and have asked several people if they had.
As far as Newbie Experience: As you know we recently saw the no-team requirement poll pass, and the reward level to non-biblepay teams set to 100%. In the next version of biblepay, we are trying to make it so a brand new user can mine with very little resistance. This means downloading the wallet, buying the UTXO amount on the exchange, downloading boinc, and clicking "Add me to Rosetta", and then click "Associate". The next version will also show how many tasks are running on the GUI - giving the user the understanding that the wallet is working (without going through RPC commands).
Having to setup PODC is by far the hardest and causes the most "resistance". Joining Biblepay is more of a issue of Religion and investment profitability and coin stability. I will be very surprised if the change increases the number of miners by a handful. |
|
|
|
thanks for the clarification, MODS: Can you move this if you think that's a better place? You can do it alone, at the bottom left there's the button "Move topic". Ah, I see it, thank you. I'm going to keep it here for now and move it if I really need to. |
|
|
|
I gave up on this coin when the lead dev (Rob) threatened to label me a satanist because I had a difference in opinion. He also thinks he ran a "successful" BOINC project in the past. In his eyes it may have been "successful". In the eyes of the BOINC community it was poorly ran and never addressed some major issues it had. An example is hard coding the BOINC data directory into your app. This is unnecessary as the BOINC client handles this. Many BOINC users deliberately move the data directory elsewhere to avoid things like apps taking too much storage or too much IO usage on the primary disk. His app was buggy and would balloon on multiple hosts with different OS's. I saw it multiple times taking up several GB's of space which it would not release without manually deleting. He refused to fix the issues the project had. And he tried to punish those that spoke out. One of the worst projects I ever contributed to and I've supported well over 100 of them.
I personally do not trust him.
I'm sorry that happened to you. His attitude towards some of us has caused a lot of anger, sadness, and some division. I hope you know that God loves you whether you are a Christian or not and that we are sticking around to see more people in need be helped. -Mike |
|
|
|
|
Welcome, feel free to post what you think about Biblepay here.
|
|
|
|
Thanks Kismar, that was a good post.
2018-08-28 06:49:21
ERROR: Found chain with blocks marked invalid
2018-08-28 06:49:21 ERROR: AcceptBlockHeader: block is marked invalid
2018-08-28 06:49:21 ERROR: invalid header received 846ef0d0c305f54a821ec9061af34a4cca1319cc84654b2e2e4f777039d6a38f
2018-08-28 06:49:21 tor: Thread interrupt
2018-08-28 06:49:21 torcontrol thread exit
2018-08-28 06:49:21 Cleaning sockets...
2018-08-28 06:49:22 PrepareShutdown: Prepare Shutdown In progress...
2018-08-28 06:49:22 Shutdown - renaming thread ...
2018-08-28 06:49:22 runCommand error: system(./biblepayd -erasechain) returned 32512
So it is revealing. On my end I need to take a look at something - it appears we do sort of jump the gun in the "Found chain with blocks marked invalid". We supposedly attempt to replay the last 205 blocks when that happens, but on your node it appears we jumped down and tried to restart it with -erasechain (see last line in the log) and that command returned an error (error 32512).
So on your end, if you are starting biblepay from an absolute path, (like from a script) that would explain 32512. Ill take a look at this. If you want autorecover to work, you could modify your script to : unalias cd && cd ~/biblepay/src/qt && ./biblepayd when it starts and then it should recover when this happens. But this is just for the time being as we make this fullproof and resilient.
2018-08-28 06:49:20 ERROR: Found chain with blocks marked invalid 2018-08-28 06:49:20 ERROR: AcceptBlockHeader: block is marked invalid 2018-08-28 06:49:20 ERROR: invalid header received 846ef0d0c305f54a821ec9061af34a4cca1319cc84654b2e2e4f777039d6a38f 2018-08-28 06:49:20 tor: Thread interrupt 2018-08-28 06:49:20 torcontrol thread exit 2018-08-28 06:49:20 scheduler thread interrupt 2018-08-28 06:49:20 msghand thread interrupt 2018-08-28 06:49:20 mnbcon thread interrupt 2018-08-28 06:49:20 addcon thread interrupt 2018-08-28 06:49:20 opencon thread interrupt 2018-08-28 06:49:20 net thread interrupt 2018-08-28 06:49:20 Cleaning sockets... 2018-08-28 06:49:20 PrepareShutdown: Prepare Shutdown In progress... 2018-08-28 06:49:20 Shutdown - renaming thread ... 2018-08-28 06:49:20 Stopped miner... stopping node 2018-08-28 06:49:20 StopNode() Got this this morning, same as above. |
|
|
|
|
Show Posts
