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

Pages: [1] 2 3
Thank you :)

Yes, there is still a lot of fine tuning required. Not all of the design is as good as I would like it, some of the sub-pages have different paddings to the border. But this will be fixed over time :)

Dear Sanctuary owners, Dear Forum users,

again it's time for a small proposal about the work done in the last weaks. Or this time, days, as most of the work one done in the last days, the first time I could work on something fun for some weeks.
Again I choosed to send in a combined proposal, at it seems a lot easier to handle than multiple smaller proposals, I hope this is ok for everybody.
The focus of work was on updating biblepay-central and make it more awesome. I wanted to make it more like a toolbox or a swiss army knife, something that is not in competition with the regular website, but adds a usefull set of functions. To make this happen, new functions were added, but also the design was changed a lot to make it look quite different from a regular website, and more like something like dash ninja.

Biblepay Central
As written above, a lot had happend with biblepay-central in the last days. The main work:

1. Proof of Distributed Computing update view (4h)
This was done shortly after the last proposal and shows the podc_updates found in the blockchain. Usefull if you want to know if the biblepay client is doing the right podc_updates without needing to sit at your pc.
It took me some time to figure out who to get these information for all users, but now it works fine.

2. Improved the documentations and How-Tos (6h)
No guide out that can't be improved. This is true for the guids of biblepay-central, too. As they seem to be one of the main sources to introduce new persons to the mining in biblepay, it is very important to keep them correct.
My work includes updating all screenshots that were out of date, fixing spelling errors, improved sentences and adding small new infos.
I also added a multi-pc mining guide and laid the foundation for an upcoming WCG guide.

3. Redesign (6h)
The old biblepay-central design was like a lot of websites, and that was a problem. It was never intended to be a competition to the main homepage, to more of an addition to that.
To ensure that all people understand that, the design was changed a lot. Plus the new design is a lot more clear, while at the same time showing more information on one screen.

4. Revamped overview (8h)
As part of the redesign, I changed the overview/startpage of biblepay-central to fit more information on it. Some of the boxes are unchanged, only reordered, but must are changed deeply to show the really usefull infos. The whole page is build from scratch, no old code was reused, as the internal working is very different. The change might be look small from the outside, but it was a very important refactoring.
This was needed, as I plan to offer and option to personalize the frontpage later on (not yet started).

5. Proposal view finished (4h)
The proposal view on biblepay-central was startes some weeks ago, but was never working as intended, a thorn in the side...
But with the redesign I found the worst bugs, and now it looks good and is working as it should.
The idea behind this section of biblepay is to give users the best possible overview of the current proposals, without hiding any useful information, and combining this with nice looking and useful charts on top. You can even visit older superblocks to see what was voted on in the past.
More features will be added in the future, like a view which masternode had voted what, plus a detail view for every proposal.

6. Masternode List (2h)
Completly new is the Masternode Section of BIblepay-Central. It gives you a nice and short overview of all existing Masternodes.
Future releases will see a detail page per Masternode, with payment infos, changelog (status changes) and other information available

7. Login & Alert (10h)
Last, but not least, is the new Login and Alert function on biblepay central. This the new release, users can register on the site and mark Masternodes, PoDC User and Proposals, so that they get alerted if something changes there. Like if a Masternode changes his status from ENABLED something else, or if a proposal gets votes. Or if a user gets a payment from podc.
This is a very important change, as it opens the gates to a lot more cool features, like the personalisation (see above).
To make this possible, most of the code had to be touched, refactored or replaced. But I'm optimistic that it is worth it.
Important: The system is NOT sending our alerts right now, as I still need to test it enough, before I "spam" users.
Right now, there are still bugs in the new biblepay-central release, but I plan to fix them asap.

Ubuntu Packages
Debug time: 5h
As most of you will know, I'm also building the Ubuntu packages for biblepay. Last month a new Ubuntu Version  18.04 was released. Sadly, Biblepay won't compile on that system right now. It took quite some time to understand the problem, or better to understand that external help was needed. It took me some hours to check all possible problems by myself, before thesnat21 could explained me the problem in detail:
The problem is not fixed yet, but at least we now know whats happening.

As always, no work on the pool is part of the proposal, but I like to use this space here to keep you updated.

1. Error informations
The pool shows (added in the last weeks) if a worker pushes invaldi solutions. Usefull to debug broken workers.

2. Rating was removed
With the improved solution checking, the rating of all miners is fine, so the function was removed. The old 150% rule is no longer used.
That's it for the pool. Not much todo here, it simply works. Stability is my main target.

Calculation in EURO:

1 BBP: EUR 0,0030 (coinmarketcap)
Per Hour: 40/h

Time Log:
Biblepay-Central: 40h
Ubuntu Packages: 5h

Budget: IT
Requested budged for this proposal:  600.000 BBP (45h @ 40)

P.S.: The proposal itself will be online soon

General Support / Re: Purepool Support
« on: May 18, 2018, 01:52:19 PM »
If you are taking enhancement requests, I'd be curious to see who the block finder for blocks on purepool are. Also, stats on which addresses find the most blocks on purepool. You know, the typical pool stats that is somewhat useful. I'm most curious though about found blocks as a ratio of pool hash power. I seem to get paid a little more than proportional of my hash rate if I throw more hash power at purepool, but that's just my guess. Having the stats would prove helpful.

Hi :)

Right now, the amount of shares/solutions mirrors quite good the amount of blocks found. This was not always the case, but with a lot of tweeking and help of Rob, the Pool is enforcing the same rules as the biblepay client for the submitted shares/solutions, and it works good.

But I will add it to the todo, but right now, my next goal is to improve biblepay-central more :)

General Support / Re: Purepool Support
« on: April 22, 2018, 03:20:25 PM »
Yes, I assigned the wallet to Rosetta on March 12 2018 and it's been successfully mining BOINC since then.

When I try to reassign it in "Add Me As A Distributed Computer Researcher" I get "ALREADY_IN_CHAIN."

My controller wallet shows a CPID, is staked, etc. This wallet doesn't show a CPID, plus it only has 10 BBP.

Edit: Just checked miner stats at:

this is new ..
List of errors related to your miner in the last 24h
Errormessage    Worker    Count
Invalid_CPID    Default    1
Invalid_CPID    TASAcer    1

Not sure if I understand what you are doing there :)
You have multiple different wallets? Or are these copies of the same wallet? If yes, please copy the wallet after you assigned the CPID.
What you can not do: Have multiple different wallets with the same CPID at the same time.  Did you tried this?

General Support / Re: Purepool Support
« on: April 22, 2018, 04:40:42 AM »
Thanks Light ... here's the info:

exec getboincinfo

  "Command": "getboincinfo",
  "CPID": "",
  "Address": "",
  "CPIDS": "",
  "CPID-Age (hours)": 423400,
  "NextSuperblockHeight": 41820,
  "NextSuperblockBudget": 1179301,
  "Total Payments (One Day)": 0,
  "Total Payments (One Week)": 0,
  "Total Budget (One Day)": 1179301,
  "Total Budget (One Week)": 8255107,
  "Superblock Count (One Week)": 8,
  "Superblock Hit Count (One Week)": 8,
  "Superblock List": "41615,41410,41205,41000,40795,40590,40385,40180",
  "Last Superblock Height": 41615,
  "Last Superblock Budget": 1179301,
  "Last Superblock Payment": -2,
  "Magnitude (One-Day)": 0,
  "Magnitude (One-Week)": 0

Looks like you didn't have a CPID assigned :) The CPID Fields should not be empty.

Did you assigned the CPID?
-> Connecting Biblepay with [email protected]

General Support / Re: Purepool Support
« on: April 20, 2018, 03:39:14 AM »
Also, I registered this miner a few days ago but still no statistics ..

Here's the biblepay.conf file ...

I don't know if it makes a difference, but BOINC is running on the same machine.

Thanks in advance!

Hi zTomasz,

I just checked your submitted solutions, I get the error: 'cpid_sig_valid': False
Something must be wrong with the cpid. Not sure what might be the reasos for that.

Can you post the full output of "exec getboincinfo"? thx :)

General Support / Re: Purepool Support
« on: April 16, 2018, 05:08:51 AM »
Hi Lichtsucher, me and another miner having a problem with Purepool. Basically, everything works, but the pool wouldn't show any miner statistics. Please visit this thread:
Hopefully, we'll find the solution

Hi GoodDeed,

the pool required a valid CPID with magnitude and payment in the last superblock (if I remember the check in the client right, this is checked in the biblepay client itself).

In your thread, it looked like this:
Total Payments (One Day): 0
Total Payments (One Week): 0
Magnitude (One-Day): 0
Magnitude (One-Week): 0

This would prevent you from working on the pool, as it would mean that you could not solve blocks.
I would need your CPID for any more checks.

General Support / Re: Purepool Support
« on: April 16, 2018, 05:04:18 AM »
Thanks Lictsucher!

I would like to know the best way to configure multiple linux & windows miners for the pool. Should each one use their own receiving address, or is there a way to have all BBP sent to one main address?

Hi zthomasz,

you can use one receiving address for all miners. Important: If you want to use the same CPID, copy the wallet.dat to all maschines. But remember that this means that the wallet is available on all systems, so better have a cold-wallet with your not-stacked coins somewhere else :)
You can also have different wallets for every pc, but then you need a working PoDC work for every one of them, with different CPIDs.

General Support / Purepool Support
« on: April 15, 2018, 06:32:02 AM »
Hi everybody,

I started this Thread for all support questions related to Purepool, it will be linked in the pool.
Feel free to ask any question you have.


Dear Sanctuary owners, Dear Forum users,

we had seem some awesome new things for Biblepay in the last days, like the upcoming Biblepay Mobile Wallet, which looks fantastic. It is great to know that Biblepay is still so powerful and alive. My own work is a little bit smaller this time, and not as great as the Mobile Wallet, but I still hope that it is part of the overall movement to make Biblepay great.
Again I choosed to send in a combined proposal, at it seems a lot easier to handle than multiple smaller proposals, I hope this is ok for everybody.

My work this month was focused on fine tuning the projects I started the last month, make them more stable, more useful and fix some small problems. I personally think that is very important to not only start projects, but to maintain them :)

Biblepay Central
It makes me really happy to see Biblepay Central used by so many users, as you can often see it in discussions when it is used in links. But nothing is perfect, and there is still a lot todo with Biblepay Central. My work this month related to Biblepay Central was:

1. Improving the Mining How-To
I'm proud of this how to, and how it helps so many newcomers. Most of the time this month I fixed smaller spelling mistakes, updated all the sections to reflect the current situation with biblepay and added more informations for experienced users. I also integrated a lot of fantastic feedback and helpful ideas from other users into the guide. Thanks to all users who submitted text for fixes for the guide.
Plus I improved the FAQ section, to help users solve some basic problems on their own. The new entries are based upon standard problems I saw in the forums.
Indeed, feedback is still very welcome :)

2. "How to get Biblepay Coins" Section added
The "How to get Biblepay Coins" section was added to help new users start with biblepay mining, as it requires some coins in their wallet. It is a small list of things users can do to start getting coins. Nothing big, but I hope it leads them in the right direction.

3. Mobile view improved
Last, still very important: I improved the mobile view of Biblepay Central by ensuring that every element of the page is responsive, even all of the tables. I used a nice trick to transform the tables into lists that works great on mobile devices.
In addition, I reworked some Graphics and Charts to fix the mobile screens, and fixed some css and html errors.

Ubuntu Packages
A lot of feedback I get suggests that the Ubuntu packages are used by many users right now. This is good, as this is reasons why they exists. But while they work good, not always was I fast enough in creating new packages when important changes happen. The reason is that I create the packages manually, as I want to ensure that everything is fine.
To solve this problem, I made some changes, but they took surprisingly much time, as launchpad is often a little bit... unstable.

1. Nightly Builds service
Yes, you read right, Biblepay now has a Ubuntu Packages Nightly Build PPA:
A new server of mine (as it contains the secret gpg keys, it can't be one of the existing servers for security reasons) is looking for new commits on the github repository of biblepay and creates a new package every hour if something had been changed.

2. Created a Biblepay Team on Launchpad
The current Biblepay Ubuntu PPA contains my own username, but it is now so widely used, that it seems better to rename it. To do that, I started a Biblepay-Team on Launchpad, so other users could be invited, too.
The Team has the same configuration, so we still have packages for ARM (2x), i386 and x64 available.

For the next month, I will maintain both PPAs (my own and the team), When I'm sure that the team PPA works well, I will anounce the end of life for my own PPA later.

3. The PPA is now self-containing
Before this change, users needed to add the biblepay AND the bitcoin PPA. But now, the biblepay PPA contains everything a user needs, including the barkley libdb packages. It took some time to make this work, as Launchpad won't compile the packages, but now it seems to be as stable as the bitcoin PPA for these packages.
It looked weird that we needed the Bitcoin PPA, I think it looks much more profesional without it.

4. Preparing for Bionic (Ubuntu 18.04)
End of this month, Ubuntu 18.04 Bionic will be released. I started to support it, but Launchpad fails at compiling packages for it right now, so we need to wait some time until packages will be available. Not all dependencies seems to be ok right now. It took some hours to understand this problem...

5. Updated the Wiki
Indeed, I updated the official Biblepay Wiki to reflect the changes above. I also removed the "Unofficial" from the PPA, as I hope that I proved my trustworthiness, so that the PPA now looks more inviting for users.

For the first time, I want to ask for support in the hosting costs. In didn't want to do this, but the number of servers is growing, and a little bit of support would be fantastic. This does NOT include the servers for Purepool.

1. Biblepay-Central
2. Biblepay-Central Explorer
3. Nightly-Build Server

Including Domains, Backups and Hosting, this makes 250 EUR for 12 month.

Indeed, as last month, these changes are not part of the proposal, but I want to list them for your information.

1. Checking the validity of the CPID
With the great help of Rob (he added a very important new output/check to the biblepay client), the pool can now check if the CPID is valid, and if the solutions submitted helps finding blocks. Makes the pool even more fair.

Calculation in EURO:

1 BBP: EUR 0,0027 (coinmarketcap)
Per Hour: 40/h

Time Log:
Biblepay-Central: 10h
Ubuntu Packages: 12h

Budget: IT
Requested budged for this proposal: 418'518 BBP (22h @ 40 + 250eur)

Archived Proposals / Re: Letter Writing Bounties
« on: April 13, 2018, 03:14:25 AM »
Sounds like a great Idea :)

Archived Proposals / Re: BiblePay mobile wallet (Android & iOS)
« on: April 04, 2018, 02:14:08 PM »
Lichtsucher is maintaining that explorer, and it's a long term commitment. I hope this information is still of any help...

Yes, you are right :)

But: I think we should only use an explorer available on the official domain for external dependencies. Makes it easier to switch the hosting if something is happening :)
And if a specific software is required, we might better create a subdomain for that, like:
This way, it is sure that an iquidus explorer is behind the domain and a switch of the software of the  the main explorer won't automatically breaks all other software (as long as the old one is available under the subdomain).

I learned the hard way that these things can happen ;D

Go for it, submit to the pool so we can vote!
Only a week to go

The proposal is online now ^^  Please vote, THANK YOU :)

Oh, and I found a small thing: the 'Discord' icon in the community tab links to Slack instead of Discord :)

Fixed ^^

I hope it will be online very soon, I asked Rob to create it, as I have not enough coins on the main pool :)

Pages: [1] 2 3