BiblePay - New Coin Launch - Official Thread

[jaapgvk]

no pool fee for whom? for all miners...by me not
when i want to write letter and all is FALSE then what?

Well, in the current (improvable) system, you could view the 'TRUE' and 'FALSE' indicators as a first glance at who's been written a letter an who's not been written a letter yet. The thing is: a letter could have been written to an orphan (see the 'outgoing letters' tab). BUT: that doesn't mean that the written letters get approved.

For example: if you look at the 'outgoing letters' tab, someone had written a letter to a sponsored child named 'Edmund Antwi'. But the thing is: his letter got a lot of downvotes, so it's never going to get send. YOU can send this orphan a letter, and when it gets upvoted, the total written letter will rise and your poolfees wil vanish (I don't know exactly if I'm right about this last part).

I think this proces could be more streamlined, but I'm sure the future looks bright in this department.

Also: when an orphan writes a SECOND letter, this also warrants a new 'poolletter' being written. But it's not clear to me how we can make this entire process more streamlined. I've made a couple of suggestions in the past. And maybe we can figure out as a community how to create a nice flow in the letter writing process.

[jaapgvk]

no pool fee for whom? for all miners...by me not
when i want to write letter and all is FALSE then what?

If I understand correctly, if there are letters sent to every child (110 children) then no-one pays the pool fee.

really?  

Yes, this is true. The fee only came into being because there were very few letters being written. So the fee is an incentive to write a letter.

[okane818]

Hello Guys,

Please share you mastenodes tut, I would like to know to setup on how to setup the masternode in my wallet.

Thank you very much and reagards

Okane Satoshi

[616westwarmoth]

Hi, I was wondering how many sanctuaries the network will need to operate efficiently?

I was looking thorough the richlist http://biblepay.inspect.network/richlist

I guess top 3 wallets are CCEX, the pool, and the wallet for charity. With a number of 1.1 million needed for a sancuary, currently that would only be 20 sanctuaries.
(a requirement of 500,000 would currently give just over 60 sanctuaries, should every eligible wallet be converted to one).

First the list you are seeing is only the top addresses.  Since many people use different addresses you're not seeing the total wallet.  For instance, my Logo Fundraiser has received just under 300K BBP, but my wallet shows I truly have my total balance from mining/donations/c-cex purchases.   Secondly, we've got two more months to mine (or buy) so another 180 Million coins into the system by Christmas, give or take.  A lot of people I imagine are getting close to the 1M target at this rate will be able to hit it.  Third, the C-cex wallet is very fat, a lot of the sell orders are very modest in price, so if the Sanctuary testing goes well, you'll see some of that be sold/bought.

I'm estimating that at least 15-30% of the total supply will go into Sanctuaries within a short period of time from the start.  If you estimate there will be roughly 400M coins at the end of the year, a 1.1M cost would mean 54 to 108 Sanctuaries at the 15-30% range.  Could be a lot more since it seems supporters of this coin are pretty dedicated.

The thing about Biblepay right now is the network operates efficiently because most everyone is running the full wallet.  Masternodes were in part invented to get around the issue Bitcoin has, most miners not contributing to the network and no incentive to run relays.  In Biblepay, the basic relay function isn't likely as important for the Sanctuaries.  Immediately the benefit is the governance function. Not to diminish the relay function, but as long as there is no other mining software, it's not such an issue.

[616westwarmoth]

Hello Guys,

Please share you mastenodes tut, I would like to know to setup on how to setup the masternode in my wallet.

Thank you very much and reagards

Okane Satoshi

http://wiki.biblepay.org/Create_Masternode

Don't forget right now Masternodes are only active in Testnet.

[slovakia]

okane818 jump to biblepay forum:  http://forum.biblepay.org


all is there: but we got problems with syncing testnet chain .. i hope that Rob will be check it where is problems...

616westwarmoth that tutorial isnt enough ...   with it nobody run it .. missing more important steps for noob,begginers ...

[bible_pay]

BIBLE_PAY

Note:   ** To write a letter to one of our orphans, from the left menu click: Orphans | Sponsored Orphan List | then Right Click on one of the Orphan records (where the NeedWritten column=TRUE). Our children LOVE to receive letters! Please write to one that needs written and you will receive the Letter Writing Bounty above once the letter is upvoted to 7 votes! **


all is FALSE ..... whats now?


so what with not sync tesnet chain?

can youh help us? thanks

Here is the thread for testnet, please post there:
http://forum.biblepay.org/index.php?topic=16.new#new

On Orphans:  Write to one who has not been written to in over 50 days while I work on the latest feature to make it easier to read.

[slovakia]

bible_pay we are on it: but you didnt answer on questions: why we cant sync chain on controller win wallets?

jaapgvk and klondike got same problems like we all

were stucked on 25684th block

[slovakia]

JCDENTON support@coinexchange.io  you can ask them ... CCEX enough for us .... BBP is very young baby ... it have to ripen

[slovakia]

beware : is all about biblepay safety???  

few days ago my machine was used for sync/flood attacking from this IP: http://whois.domaintools.com/183.60.110.239


on my private machine XEON 4110 128GB RAM im installed only BIBLEPAY mining!!!! it was clean ubuntu 16.04 machine,manually installed biblepay daemon from tutorial
machine is on 4/4GBit




LOGS ----------------------------------
        Attack detail : 14Kpps/3999Mbps
        dateTime                   srcIp:srcPort           dstIp:dstPort      
    protocol flags       bytes reason              
        2017.10.21 18:51:27 CEST   :61919    183.60.110.239:80  
    TCP      SYN           901 ATTACK:TCP_SYN      
        2017.10.21 18:51:27 CEST   :39131    183.60.110.239:80  
    TCP      SYN           906 ATTACK:TCP_SYN      
        2017.10.21 18:51:27 CEST   :29081    183.60.110.239:80  
    TCP      SYN           897 ATTACK:TCP_SYN      
        2017.10.21 18:51:27 CEST   :52413    183.60.110.239:80  
    TCP      SYN           912 ATTACK:TCP_SYN      
        2017.10.21 18:51:27 CEST   :14344    183.60.110.239:80  
    TCP      SYN           892 ATTACK:TCP_SYN      
        2017.10.21 18:51:27 CEST   :59386    183.60.110.239:80  
    TCP      SYN           925 ATTACK:TCP_SYN      
        2017.10.21 18:51:27 CEST   :62291    183.60.110.239:80  
    TCP      SYN           893 ATTACK:TCP_SYN      
        2017.10.21 18:51:27 CEST   :64251    183.60.110.239:80  
    TCP      SYN           912 ATTACK:TCP_SYN      
        2017.10.21 18:51:27 CEST   :42818    183.60.110.239:80  
    TCP      SYN           887 ATTACK:TCP_SYN      
        2017.10.21 18:51:27 CEST   :48614    183.60.110.239:80  
    TCP      SYN           891 ATTACK:TCP_SYN      
        2017.10.21 18:51:27 CEST   :49110    183.60.110.239:80  
    TCP      SYN           905 ATTACK:TCP_SYN      
        2017.10.21 18:51:27 CEST   :37942    183.60.110.239:80  
    TCP      SYN           906 ATTACK:TCP_SYN      
        2017.10.21 18:51:27 CEST   :57811    183.60.110.239:80  
    TCP      SYN           905 ATTACK:TCP_SYN      
        2017.10.21 18:51:27 CEST   :64097    183.60.110.239:80  
    TCP      SYN           896 ATTACK:TCP_SYN      
        2017.10.21 18:51:27 CEST   :64247    183.60.110.239:80  
    TCP      SYN           918 ATTACK:TCP_SYN      
        2017.10.21 18:51:27 CEST   :25620    183.60.110.239:80  
    TCP      SYN           910 ATTACK:TCP_SYN      
        2017.10.21 18:51:27 CEST   :6072     183.60.110.239:80  
    TCP      SYN           933 ATTACK:TCP_SYN      
        2017.10.21 18:51:27 CEST   :3695     183.60.110.239:80  
    TCP      SYN           932 ATTACK:TCP_SYN      
        2017.10.21 18:51:27 CEST   :52484    183.60.110.239:80  
    TCP      SYN           907 ATTACK:TCP_SYN      
        2017.10.21 18:51:27 CEST   :6986     183.60.110.239:80  
    TCP      SYN           917 ATTACK:TCP_SYN      

[jaapgvk]

Is this the picture for the new biblepay coin logo?
I am looking forward to using the new coin picture at twitter and at the blog.
Should I wait, or is this the picture to use?

Our leading artist redid the image to make it a more pronounced cross.  Do we like it better this way or the other?

They're linking in the Biblepay Forum.

Wow!  Thats pretty stunning.  Imho, I think I like B a little more than A, since A is a little "Gold" looking, Ill comment over there.  Also, I think this contrasts really well on most pages and contrasts itself also.


Heres the link:

http://forum.biblepay.org/index.php?topic=25.0

In my opinion, I would wait a bit, at least until everything is official

[znffal]

Hi, I was wondering how many sanctuaries the network will need to operate efficiently?

I was looking thorough the richlist http://biblepay.inspect.network/richlist

I guess top 3 wallets are CCEX, the pool, and the wallet for charity. With a number of 1.1 million needed for a sancuary, currently that would only be 20 sanctuaries.
(a requirement of 500,000 would currently give just over 60 sanctuaries, should every eligible wallet be converted to one).

First the list you are seeing is only the top addresses.  Since many people use different addresses you're not seeing the total wallet.  For instance, my Logo Fundraiser has received just under 300K BBP, but my wallet shows I truly have my total balance from mining/donations/c-cex purchases.   Secondly, we've got two more months to mine (or buy) so another 180 Million coins into the system by Christmas, give or take.  A lot of people I imagine are getting close to the 1M target at this rate will be able to hit it.  Third, the C-cex wallet is very fat, a lot of the sell orders are very modest in price, so if the Sanctuary testing goes well, you'll see some of that be sold/bought.

I'm estimating that at least 15-30% of the total supply will go into Sanctuaries within a short period of time from the start.  If you estimate there will be roughly 400M coins at the end of the year, a 1.1M cost would mean 54 to 108 Sanctuaries at the 15-30% range.  Could be a lot more since it seems supporters of this coin are pretty dedicated.

The thing about Biblepay right now is the network operates efficiently because most everyone is running the full wallet.  Masternodes were in part invented to get around the issue Bitcoin has, most miners not contributing to the network and no incentive to run relays.  In Biblepay, the basic relay function isn't likely as important for the Sanctuaries.  Immediately the benefit is the governance function. Not to diminish the relay function, but as long as there is no other mining software, it's not such an issue.

Yes thanks. I forgot that people have more than one address in their wallet.
Thanks!

[znffal]

So if I wanted to get to the 1.1m mark by Christmas I would need more machines to do this.
Has anyone mined BBP on the cloud?
Where is this possible?


Or is it cheaper to just make an account and buy on CCEX?

Thanks

[bible_pay]

So if I wanted to get to the 1.1m mark by Christmas I would need more machines to do this.
Has anyone mined BBP on the cloud?
Where is this possible?


Or is it cheaper to just make an account and buy on CCEX?

Thanks

Check out the testnet thread
http://forum.biblepay.org/index.php?topic=16.new#new

The $10 monthly Vultr VPS should work fine and let you transition from mining to mining + sanctuary.

[znffal]

So if I wanted to get to the 1.1m mark by Christmas I would need more machines to do this.
Has anyone mined BBP on the cloud?
Where is this possible?


Or is it cheaper to just make an account and buy on CCEX?

Thanks

Check out the testnet thread
http://forum.biblepay.org/index.php?topic=16.new#new

The $10 monthly Vultr VPS should work fine and let you transition from mining to mining + sanctuary.

Thanks Rob, do you know roughly the HPS for 1 of those machines?

[bible_pay]

So if I wanted to get to the 1.1m mark by Christmas I would need more machines to do this.
Has anyone mined BBP on the cloud?
Where is this possible?


Or is it cheaper to just make an account and buy on CCEX?

Thanks

Check out the testnet thread
http://forum.biblepay.org/index.php?topic=16.new#new

The $10 monthly Vultr VPS should work fine and let you transition from mining to mining + sanctuary.

Thanks Rob, do you know roughly the HPS for 1 of those machines?

It looks like right now, Im getting 20k HPS on the $10 per month linux box, 35k HPS on the $40 per month linux box, and about 20k hps on the $60 per month windows box (but its the pool, and I only run it at 2k hps LOL to keep it free).  Im running debian jessie 64 on the two linux boxes.

In f8000, you should see more like 20,35,35 across the boxes, except the hps will be lower (we are just about to test that in testnet next).

[znffal]

So if I wanted to get to the 1.1m mark by Christmas I would need more machines to do this.
Has anyone mined BBP on the cloud?
Where is this possible?


Or is it cheaper to just make an account and buy on CCEX?

Thanks

Check out the testnet thread
http://forum.biblepay.org/index.php?topic=16.new#new

The $10 monthly Vultr VPS should work fine and let you transition from mining to mining + sanctuary.

Thanks Rob, do you know roughly the HPS for 1 of those machines?

It looks like right now, Im getting 20k HPS on the $10 per month linux box, 35k HPS on the $40 per month linux box, and about 20k hps on the $60 per month windows box (but its the pool, and I only run it at 2k hps LOL to keep it free).  Im running debian jessie 64 on the two linux boxes.

In f8000, you should see more like 20,35,35 across the boxes, except the hps will be lower (we are just about to test that in testnet next).

Cool, thanks for that!

[bible_pay]

I was thinking of ways to make us a team player in the great tribulation, after reading that reddit post where someone asked us if we were the mark of the beast.

I was thinking, how can we create an outline of features that would provide value during the great tribulation, instead of rolling over and dying.

So far here is what came to mind:

- Reverse implosion database, full of phone numbers, addresses, contacts and background info on Christian members
- Biblepay Emergency mode, where each step of the ledger is either manually committed, or synced via an alternative network other than cat5/wifi
- Silver coins, survival food for sale for biblepay, from the pool (and hopefully in wallet eventually)
- Some groundbreaking feature that gives intrinsic value to a coin when the blockchain stops (this is if the internet completely goes down including wifi), or, an alternative idea that keeps the chain rolling
- A simpler protocol, one that can be executed by hand (probably not realistic)

A long time ago, while working for a blood delivery company, we had an emergency mode that we entered if the power and LAN went out.  We would take orders from hospitals, write them down manually, and if possibly print all the blood drivers routes out manually, and continue operations by moving papers around like it was in the 60s.  I was thinking, if we are fortunate enough in the great trib to move anything around, we could use this as one idea.

In the most basic sense, it would be valuable to have maps of where the Christians are (IE US), and band together and share our food and water, and help each other.  So of course with the block chain being private by default, most everyone will not want to share all this personal info by default.  But one option is maybe we build in an implosion database.  We could make it encrypt 'contact records' entered into the UI with a key on the client side that corresponds to an unlock key that is broadcast back to unlock all the data but only if the chain does not advance for 7 days straight.  Then, each users copy is fully readable (ie the whole record database).  

[nguli]

heu dev, any airdrop or bounty campaign?

[slovakia]

BIBLEPAY
testnet is still broken with syncing controller wallets ...

edit://  win wallet updated to v152 now and still problems with syncing testnet