bible_pay (OP)
Full Member
 Offline
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
|
 |
October 11, 2018, 03:51:58 PM |
|
Status update on the latest mandatory version:
The version that has been available for download - 1.1.5.7+ is fine for all intents and purposes, but we are adding some 'nice to have leisure' features now.
Currently I'm migrating our orphans individual bio records into IPFS so we can display them in the core wallet.
We will also have a bug fix in business objects that allows quicker navigation.
MIP has committed to adding a Church Tithe button to the mobile wallet! This should be really awesome, and I'm very excited about that.
MIP and I are also working through the Apple policies to get the Apple version of BiblePay mobile wallet released.
I'll be starting on in-wallet letter writing next - I believe we are going to go all the way with BiblePay core, and start moving things from the pool into the core wallet. We will provide the ability to write orphan letters, list the letters, upvote the letters, etc. The content-economy discussion will be a whole separate issue (having to do with content creation, uploading Christian videos, IPFS rewards, voting rewards etc).
|
|
|
|
vahtis
Newbie
Offline
Activity: 153
Merit: 0
|
|
October 11, 2018, 04:12:04 PM |
|
Status update on the latest mandatory version:
The version that has been available for download - 1.1.5.7+ is fine for all intents and purposes, but we are adding some 'nice to have leisure' features now.
Currently I'm migrating our orphans individual bio records into IPFS so we can display them in the core wallet.
We will also have a bug fix in business objects that allows quicker navigation.
MIP has committed to adding a Church Tithe button to the mobile wallet! This should be really awesome, and I'm very excited about that.
MIP and I are also working through the Apple policies to get the Apple version of BiblePay mobile wallet released.
I'll be starting on in-wallet letter writing next - I believe we are going to go all the way with BiblePay core, and start moving things from the pool into the core wallet. We will provide the ability to write orphan letters, list the letters, upvote the letters, etc. The content-economy discussion will be a whole separate issue (having to do with content creation, uploading Christian videos, IPFS rewards, voting rewards etc).
I like reading progress reports like this  |
|
|
|
|
bbptoshi
Copper Member
Newbie
Offline
Activity: 39
Merit: 0
|
|
October 11, 2018, 09:39:13 PM |
|
Thanks everyone for all of your hard work on BBP recently. With the stock market turning down this week, it seems financial instability is on the rise, and it is comforting that Biblepay exists as a fallback system. All the hard work has made this happen, and the work in progress gives confidence in its future.
Just to mention a technical topic on my mind, I usually keep my wallet computer off, and turn it on each day and send a "exec podcupdate true" PODC update manually. However, sometimes the wallet sends an update on its own at the same time, and one PODCupdate goes out with only the remainder of coins staked. This would reduce my daily payment unless I wait 6 confirmations and send out a new one. Is there anyway to have it not send 2 updates in this case? Not sure how many people update like this, but I thought I'd ask the question.
Best to all,
bbptoshi
|
|
|
|
|
|
|
|
sunk818
|
|
October 12, 2018, 01:44:07 AM |
|
Thanks everyone for all of your hard work on BBP recently. With the stock market turning down this week, it seems financial instability is on the rise, and it is comforting that Biblepay exists as a fallback system. All the hard work has made this happen, and the work in progress gives confidence in its future.
Alternatively, nothing like a down turn in the crypto market to light a refining fire encouraging innovation. |
|
|
|
|
togoshigekata
|
|
October 12, 2018, 03:18:32 AM
Last edit: October 12, 2018, 03:58:41 AM by togoshigekata |
|
|
|
|
|
secoccular
Jr. Member
Offline
Activity: 226
Merit: 2
|
|
October 12, 2018, 06:40:54 AM |
|
I may have misread, but I read it as coin mixing isn't safe because an unfriendly masternode might see both side of the transaction? Not that the entire private pay could be easily compromised. Don't the masternodes have to see the addresses on both sides? The more I read about Dash, the less I like it. The emphasis on masternodes lacks the graceful democracy that BTC was based upon. It seems those with the most coins get more coins? Also, that kind of structure (masternodes) requires trust and ever-growing governance. I think that it can create a closed-loop, where new folks don't catch up as well. Anyway, BBP is it's own thing, and hopefully will avoid some of the fighting that seems to plague the Dash community. |
|
|
|
|
MIP
Newbie
Offline
Activity: 362
Merit: 0
|
|
October 12, 2018, 08:05:27 AM |
|
His response: "I can’t take the opinions of a religious cryptocurrency seriously."
Not being taken seriously is one of the first steps in the ladder to success. I would consider it as a good sign. |
|
|
|
|
thesnat21
Jr. Member
Offline
Activity: 490
Merit: 4
|
|
October 12, 2018, 11:21:19 AM |
|
Thanks everyone for all of your hard work on BBP recently. With the stock market turning down this week, it seems financial instability is on the rise, and it is comforting that Biblepay exists as a fallback system. All the hard work has made this happen, and the work in progress gives confidence in its future.
Just to mention a technical topic on my mind, I usually keep my wallet computer off, and turn it on each day and send a "exec podcupdate true" PODC update manually. However, sometimes the wallet sends an update on its own at the same time, and one PODCupdate goes out with only the remainder of coins staked. This would reduce my daily payment unless I wait 6 confirmations and send out a new one. Is there anyway to have it not send 2 updates in this case? Not sure how many people update like this, but I thought I'd ask the question.
Best to all,
bbptoshi
This is similar to what happens if you run more than 1 wallet without the utxooverride. In your case I think the simplest solution would be to either set gen=0 in the config since you are doing the send yourself, or just let the wallet sync and sit a few minutes until it creates the transaction. His response: "I can’t take the opinions of a religious cryptocurrency seriously."
Not being taken seriously is one of the first steps in the ladder to success. I would consider it as a good sign. It's still sharing us with the public even if he is trying to insult us. |
|
|
|
|
|
jaapgvk
|
|
October 12, 2018, 11:59:43 AM |
|
Status update on the latest mandatory version:
The version that has been available for download - 1.1.5.7+ is fine for all intents and purposes, but we are adding some 'nice to have leisure' features now.
Currently I'm migrating our orphans individual bio records into IPFS so we can display them in the core wallet.
We will also have a bug fix in business objects that allows quicker navigation.
MIP has committed to adding a Church Tithe button to the mobile wallet! This should be really awesome, and I'm very excited about that.
MIP and I are also working through the Apple policies to get the Apple version of BiblePay mobile wallet released.
I'll be starting on in-wallet letter writing next - I believe we are going to go all the way with BiblePay core, and start moving things from the pool into the core wallet. We will provide the ability to write orphan letters, list the letters, upvote the letters, etc. The content-economy discussion will be a whole separate issue (having to do with content creation, uploading Christian videos, IPFS rewards, voting rewards etc).
Awesome! I really like the idea of in-wallet letter writing. That should keep the barrier as low as possible, especially with things like voting on letters. Every times you open your wallet, your options are staring you right in the face. It gets really easy to up/downvote some letters every once in a while. |
|
|
|
thesnat21
Jr. Member
Offline
Activity: 490
Merit: 4
|
|
October 12, 2018, 03:39:23 PM
Last edit: October 12, 2018, 03:52:37 PM by thesnat21 |
|
Hello, Due to technological incompatibilities, Mintnodes.com is discontinuing the BiblePay (BBP) Clusternode service. Please withdraw your coins by November 1, 2018. Thanks, Mintnodes.com Support Team https://www.mintnodes.comI've asked what the issue was, will let you know if there is anything we need to change. |
|
|
|
|
|
sunk818
|
|
October 12, 2018, 03:57:17 PM |
|
Hello, Due to technological incompatibilities, Mintnodes.com is discontinuing the BiblePay (BBP) Clusternode service. Please withdraw your coins by November 1, 2018. Thanks, Mintnodes.com Support Team https://www.mintnodes.comI've asked what the issue was, will let you know if there is anything we need to change. Random fork this week and watchmen requirement doesn't help |
|
|
|
thesnat21
Jr. Member
Offline
Activity: 490
Merit: 4
|
|
October 12, 2018, 04:19:34 PM |
|
Random fork this week and watchmen requirement doesn't help
Other coins require sentinal, watchman is just a variation of that. The fork thing makes sense. |
|
|
|
|
|
sunk818
|
|
October 12, 2018, 04:45:26 PM |
|
Random fork this week and watchmen requirement doesn't help
Other coins require sentinal, watchman is just a variation of that. The fork thing makes sense. I see. What kind of issues do other master nodes experience? Hard to compare (besides gridcoin) because BiblePay has a lot of unique features. Investors having hard time with bbp unless they can build their own master nodes. I think mintnodes is a great idea and we should work towards keeping them with BiblePay. |
|
|
|
thesnat21
Jr. Member
Offline
Activity: 490
Merit: 4
|
|
October 12, 2018, 05:21:54 PM |
|
Other coins require sentinal, watchman is just a variation of that. The fork thing makes sense.
I see. What kind of issues do other master nodes experience? Hard to compare (besides gridcoin) because BiblePay has a lot of unique features. Investors having hard time with bbp unless they can build their own master nodes. I think mintnodes is a great idea and we should work towards keeping them with BiblePay. I'm trying to engage them, so far no response. |
|
|
|
|
MIP
Newbie
Offline
Activity: 362
Merit: 0
|
|
October 12, 2018, 05:46:25 PM |
|
I'm trying to engage them, so far no response.
Refer them to masternode install script we prepared. It takes care of everything and avoids the legwork. Regarding forks, I don’t know of any non-PoBH mining node (like a MN) affected. |
|
|
|
|
bible_pay (OP)
Full Member
Offline
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
|
|
October 12, 2018, 06:13:16 PM |
|
Thanks everyone for all of your hard work on BBP recently. With the stock market turning down this week, it seems financial instability is on the rise, and it is comforting that Biblepay exists as a fallback system. All the hard work has made this happen, and the work in progress gives confidence in its future.
Just to mention a technical topic on my mind, I usually keep my wallet computer off, and turn it on each day and send a "exec podcupdate true" PODC update manually. However, sometimes the wallet sends an update on its own at the same time, and one PODCupdate goes out with only the remainder of coins staked. This would reduce my daily payment unless I wait 6 confirmations and send out a new one. Is there anyway to have it not send 2 updates in this case? Not sure how many people update like this, but I thought I'd ask the question.
Best to all,
bbptoshi
Thank you for the compliments; they go a long way in the desert we are currently in . As far as the wallet re-sending another UTXO (back to back), we actually have a line of code in the wallet designed to prevent a re-send (its basically checking to see if one was sent within the last 4 hours), however, it relies on the tx being more than 1 mature - which probably was not the case. I'll look at this issue. |
|
|
|
bible_pay (OP)
Full Member
Offline
Activity: 1176
Merit: 215
Jesus is the King of Kings and Lord of Lords
|
|
October 12, 2018, 06:17:41 PM |
|
I'm trying to engage them, so far no response.
Refer them to masternode install script we prepared. It takes care of everything and avoids the legwork. Regarding forks, I don’t know of any non-PoBH mining node (like a MN) affected. I didn't know we had the random fork this week, I thought we have been pretty solid for 45 days or so. But on the positive side, this is with the old codebase running (the upgraded block sync code does not start til 77000) - hopefully God willing this new start extends our current stability from 45 days to more like 365 days without forced reboots or reindexes. |
|
|
|
|
jaapgvk
|
|
October 12, 2018, 06:19:47 PM |
|
I'm trying to engage them, so far no response.
Refer them to masternode install script we prepared. It takes care of everything and avoids the legwork. Regarding forks, I don’t know of any non-PoBH mining node (like a MN) affected. I didn't know we had the random fork this week, I thought we have been pretty solid for 45 days or so. But on the positive side, this is with the old codebase running (the upgraded block sync code does not start til 77000) - hopefully God willing this new start extends our current stability from 45 days to more like 365 days without forced reboots or reindexes. Didn't know about the fork either... And I also reached out to mintnodes. Good idea about mentioning the install-script MIP! If they reply to me I'll sure mention it. |
|
|
|
|
togoshigekata
|
|
October 12, 2018, 06:27:00 PM |
|
I may have misread, but I read it as coin mixing isn't safe because an unfriendly masternode might see both side of the transaction? Not that the entire private pay could be easily compromised. Don't the masternodes have to see the addresses on both sides? PrivateSend is basically a decentralized Coin Mixer https://wiki.biblepay.org/PrivateSendBitcoin has coin mixers, but they are 3rd party services that you have to trust, with Dash its built in. The only way to break PrivateSend is to gain computer access to a majority of the masternodes on the network (Also the less rounds of mixing a user performs the easier it is to break PrivateSend for that user) This is a chart of how many masternodes a malicious entity would need to own in order to successfuly track a privatesend https://i.imgur.com/FfxkEBf.pngThe more I read about Dash, the less I like it. The emphasis on masternodes lacks the graceful democracy that BTC was based upon. It seems those with the most coins get more coins? Also, that kind of structure (masternodes) requires trust and ever-growing governance. I think that it can create a closed-loop, where new folks don't catch up as well. Anyway, BBP is it's own thing, and hopefully will avoid some of the fighting that seems to plague the Dash community.
If your investing in BiblePay then your currently investing in the Dash model, we are a fork of Dash. Bitcoin cant make decisions, there have been 16+ forks of Bitcoin, and Bitcoin Cash was a huge mess, Dash on the other hand had a vote on the block size and all came to agreement and did not fork Dash can pay people, how do Bitcoin devs get paid? If theyre paid by outside forces are there strings attached? How does Bitcoin fund future development? How do they get money? Who better to make decisions about BiblePay then the people with the most money on the line, the most skin in the game? Please check out this wiki page: Understanding the BiblePay Masternode Governance and Monthly Budget Systemhttp://wiki.biblepay.org/UnderstandingGovernancePlease bring up other governance models if you think there is a better one, Im curious to learn more! |
|
|
|
|
