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
1
Mining - General / Purepool Biblepay Pool
« on: February 21, 2018, 04:16:35 am »
Hi everyone,

I just realized that I hadn't announced the Purepool Biblepay Pool here in the Forum.
As most users might now, more is always better. And as long as PoDC isn't ready, a pool is always a good way to earn coins :)

If you are looking for an easy to use pool, you might try the Purepool Biblepay pool: https://www.purepool.org
It is easy to setup and use, and is - for now - without a pool fee.


The source code will be release in the next days, when all is tested well on reference purepool installation.

2
Were you also mining this whole time?

Yes, I had forgotten the maschine over the weekend, but it was mining and had found a lot of blocks on the testnet.

3
I'm not sure if I do it right, I had a POL error message the whole time:
"proof_of_loyalty_errors": "BALANCE TOO LOW TO STAKE"

{
  "Command": "stakebalance",
  "StakeBalance": 0
}

{
  "walletversion": 61000,
  "balance": 10418865.62299800,
  "retirement_account_balance": 0,
  "unconfirmed_balance": 0.00000000,
  "immature_balance": 752689.42450000,
  "txcount": 810,
  "keypoololdest": 1516891781,
  "keypoolsize": 1001,
  "keys_left": 999,
  "paytxfee": 0.00000000
}


4
I Rob, I want to start testing it, too.

Can you send me some coins to my testnet Wallet: yQiXLmo6a1MB169ipHhfdqfjshw9gEns1f

5
The build for Version 1.0.8.4 is ready.
By the way, I also added support for arm64 and armhf, these packages are compiled, too. But we need somebody to test them, I have no supported arm system here.

By the way, hope more more sanctuary owners will upvote, THX a lot :)

6
Support and Troubleshooting / Re: Slack invite link no longer working?
« on: January 21, 2018, 01:39:45 pm »
Thank you, the new link worked :)

7
Support and Troubleshooting / Slack invite link no longer working?
« on: January 21, 2018, 06:23:32 am »
Hi everybody,

in some posts it is said that some discussions are held in slack, so I tried to join it, too, but the Link available on reddit only says that the Link is no longer active.

Is slack no longer used, or is only the link out of date?

Greetings

8
Small note:
My hope would be, that the core team would create the packages in the future. Do make that possible, I created a howto on the whole process:
https://github.com/Lichtsucher/biblepay-deb-builder

This way, the packages would be as trustworthy as the whole project. In the meantime. I will keep them uptodate on my PPA :)

9
How will the PPA repository be updated with new BiblePay versions in the future?

Yes, I will update it with new Version as soon as I see them. For now, it it a little bit more complicated, as there is a waiting pull request on github that is requried for the package building. In the meantime, I build from a fork that has the changed (but nothing else changed).  Hope the changes will be included very soon :)

I just submited 10.8.3c as new version, launchpad is building it right now. I also added Ubuntu 17.10 (Artful) as target distribution.

@616westwarmoth
togoshigekata already created the proposal, but thx :)

10
A word about the speed of the precompiled deb files:
I'm currently testing the package on an i7-7700 compared to a locally compiled version with standard compile parameters (as given in the reddit howto).
Both versions show nearly the identical hps, it seems that there is no significant speed difference on that system.

11
Dear Sanctuary owners, Dear Forum users,

with great joy I want to announce the first version of an (unofficial) ubuntu package repository to the Biblepay community. In the course of a couple of days containing very hard and long work, I was able to bring the existing biblepay code to the modern world of package management.

URL of the PPA repository: https://launchpad.net/~lichtsucher/+archive/ubuntu/biblepay

But it is not only the repository, it is the whole workflow of creating and managing ubuntu packages that was solved. A new subproject (https://github.com/Lichtsucher/biblepay-deb-builder) was started that streamlines the process and make it available for everybody. Documentation included. An official repository would be very easy to setup and maintain.

In the hopes that future users of Biblepay will benefit of the very easy installation and easy-to-update nature of such packages, I hope that you will accept my proposal.

With all that said, I really need to get some sleep ;)

Features for the users
  • Easy installation, Desktop with Icons and Menu entries
  • Separate Packages for biblepay-qt and biblepayd/biblepay-cli
  • Quick update with apt-get upgrade
  • No compilation hazzle, seconds of download time version minutes or hours of compilation time
  • Easy-to-follow howto for installation in the wiki: http://wiki.biblepay.org/Ubuntu_Packages
  • Launchpad PPA is more trustworthy then most binary releases *1
  • Binaries for different ubuntu versions and plattforms (i386 & amd64)

*1 = The code is build by launchpad and everybody can download the source code that was used to verify it.

Features for the developers
  • New project that simplifies the workflow: https://github.com/Lichtsucher/biblepay-deb-builder
  • Workflow for upload to PPA
  • Supports local deb building, too (like for custom builds)
  • Less questions from newcomers about problems with the compilation
  • Creating of deb file requires only 2 short steps: Update changelog + build/upload
  • Builds multiple versions at the same time: Multiple ubuntu releases and plattforms (i386 & amd64) build with one run

Benefits for Biblepay
  • Looks more professional than requiring to compile the code
  • A must have for desktop users on Ubuntu, compilation isn't common there
  • Less Users are scared away (by compiling the source code)
  • More users = better for the project as a whole
  • Helps admins of bigger serverfarms to keep there servers up-to-date

Work done
  • Preparation: Investigation the best way of deploying deb files for a project like biblepay. Tested repositories via webserver, Amazon S3 upload and PPA. PPA won, as it was the easiest on the long run.
  • Started the project "biblepay-deb-builder" to local build deb-files
  • Fixed the old contrib/debian folder. Created pull request (https://github.com/biblepay/biblepay/pull/11)
  • Bug hunt: Got problems with qt4 build of the ui that costs me hours of understanding it, seems to be a bug in biblepay that was already fixed in dashpay: https://github.com/dashpay/dash/pull/1672
  • Improved biblepay-deb-builder to support PPA Builds (source code builds)
  • Improved the script to use Docker, to support different ubuntu versions
  • Wrote a detailed howto for the setup of a launchpad PPA
  • Wrote a Wiki page how to install the debian package
  • Tested the whole setup on Ubuntu 16.04, Ubuntu 14.04 (i386 and x86) with server version and desktop version, plus Lubuntu as a test for a more exotic version.

I still want to create a version for debian to, I'm currently investigating how to make that possible with PPA.

Calculation
Calculation in EURO:

1 BBP: EUR 0,0055 (19 Jan 2018, 10:00 CET, coinmarketcap)
30EUR/h - Local low rate for a normal DevOp

Time log:
5 hrs: Preparation and Investigation
15 hrs: Project setup, contrib/debian fixing, bug searching, first builds
15 hrs: Add PPA support, PPA setup, troubleshooting (ppa has horrible error messages...), ppa documentation (README.md)
5 hrs: Installation Wiki and testing the setup with different ubuntu versions
= 40 hrs

Budget: IT
Requested budged for this proposal: 216'785 BBP (40 hrs @ 30 EUR + costs of the proposal)


Relevant Links:
Biblepay-Deb-Builder:
https://github.com/Lichtsucher/biblepay-deb-builder

Launchpad PPA Repository:
https://launchpad.net/~lichtsucher/+archive/ubuntu/biblepay

Pull Request:
https://github.com/biblepay/biblepay/pull/11




12
Mining - General / Re: Mining limited to 40 Cores?
« on: January 18, 2018, 09:12:34 am »
My advice: setup a second wallet and miner in a docker image, that's the easiest way to setup another wallet at the same time on the same ubuntu system.

Might help:
https://hub.docker.com/r/gagaha/biblepay/~/dockerfile/

13
General Discussion / Re: Idea for two proposals
« on: January 15, 2018, 02:19:46 am »
Hi 616westwarmoth,

thanks for your answer, that is already helping me.

About the deb-packages: You are right that the compiling isn't that complex, in fact is quite easy. But at the same time, it will discourage users, even I was nearly skipping biblepay because of that. It is an unrequired hassle, and I think a modern software should be as easy to use as possible. My target would be to make it as easy as possible for the devs to build and deploy these packages, with documentation and everything already solved, so that they will not days behind, but more or less available at the same time as the windows binaries.
I'm not sure that system the devs use for everyday work, windows or linux. Indeed, if all of them use Windows, building ubuntu packages would require a little bit more work, but that could be solved by a simple VM.


I also think that the pool software is more important, as it seems to be a real problem at the moment. What I would do first here is to documentate the existing protocol and most important functions. As I found out, biblebay has its own custom protocoll between the miner and the pool, so an existing pool software would need to be changed to use it.
I would prefer to write a standalone software from the start, as it would not only be a pool software, but also a reference implementation, that could be the source for other pool software. I think it would not solve a lot of problems, if the next standard pool software is even more complicated then the existing one.
But I'm very interessted in feedback about that, in anycase, we would need a good documentation, I think that should be the start for every step. And Indeed I would try to create one with the devs.

At the moment, I invested around 4 hours investigating the source code of the pool, with I will use as a base for a wiki page I try to start today. I also played around with the existing debian code in the client and found some problems there, but I was not sure if I should invest more time into the debian package or pool :) But as said, building the package for debian will not be the most problematic part there, I will take more time to test them and write the docs for the developers and users who want to compile it as debian package for them self.

About the budget: Both projects would be part of the IT budget. There do not seems to be that many projects there for the moment, is that right? Is there enough budget for these, I would calculate with 30 EUR/h.

14
General Discussion / Idea for two proposals
« on: January 14, 2018, 01:06:07 pm »
Hi everyone,

after some time doing deeper into the project, I realized that there might be two thing that I can do that might be usefull for the project.
Both might be good proposals, got before I post them, I wanted to ask about your opinions.

1. Debian/Ubuntu packages
A lot of the current users seems to use Linux, and I assume a lot of them use debian or ubuntu, as it is with a lot of projects. While compiling is not super problematic, it might shy away some users, or limit there use.
There are some older parts for debian already in the project, but I played around with them, they do not seem to work properly anymore, plus there is no documentation. Plus a good project would provide an apt source for easier installation.
With cleanup, documentation and helping the devs to setup a apt source (sensible part, should be hosted/managed by the core team, I think), I thing it will be around 30-40 hours. Testing will take most of the time, I learned that the hard way in a previos project where I did the same ;)

2. Making a better pool software
The current pool seems to work most of the time, but the software is windows only, a little bit of a mess (mixed UI and Pool code), no documentation ...
My idea would be to write a core only, that means the part that speaks to the miners, plus an API that is used by the real ui (the current one?) to get the "numbers" (hashrate and so on). Orphan letters anhd so on would be separated. Plus writing a mini-ui for Pools that do not need the full features of the main pool.
The code would be written in a ways that is would be easy to understand, like a "documentation as code" ;)
I do not now how much time it will take, as it will require a lot of understanding of the current code, which is not that easy. I already followed everything from readytomine2 to solution taking and when the system tries to identify found blocks. But some lines are very cryptocoin specific, so I would need help from the code team.
I would asume that this would require around 40-50hours on my side, if the old code can be explained to me. I would use Python, with mysql or postgre as standard dbs, but we can try to make it mssql compatible, too.

What do you think, would it be usefull to create proposals out of one or two of these projects? Is that something worthy the time? And is it realistic that one of these is accepted as proposals?
Are proposals normaly accepted before the work begins, or after it is finished?

15
BiblePay - New Coin Launch / Inner working of the the pool
« on: January 12, 2018, 09:57:39 am »
Hi everyone,

I sometimes love dive into more details of a software, but with the mining pool software of biblepay, I had some problems.
I could not really find out how a block is found / how the pool knows about it. Is there any technical document about that, which explains the work between the miner and the pool in detail?
I tried to compare it to information I found about pools of other coins, but these seems to  work different (most miners on other coins are no full nodes, right?)
Maybe I miss the right code, the source code is a little bit hard to read, most of the time I only found code for the frontend ;)

Thx for the explanation

Pages: [1] 2