Search content
Sort by

Showing 11 of 11 results by fjavi
Post
Topic
Board Announcements (Altcoins)
Re: BiblePay | Masternodes | Sanctuaries | POBH - ASIC Resistant | 10% ORPHANS
by
fjavi
on 06/05/2018, 10:30:57 UTC
Please vote for Biblepay inclusion in mnode.club cool Masternodes monitoring website

https://mnode.club/g/coinvote/BBP
(Registration required)
Thanks!
Post
Topic
Board Announcements (Altcoins)
Re: SatoshiCoin
by
fjavi
on 04/05/2018, 08:11:17 UTC
From the website:

Block Rewards
0-10080 - 16 SATC
10080-40320 - 17 SATC
40320-80640 - 18 SATC
80640-120960 - 20 SATC
120960 and higher - 24 SATC

However, how can be supply limited to any number, if block rewards are increasing?

Thank you, I will follow up this interesting project
Post
Topic
Board Announcements (Altcoins)
Re: BiblePay | Masternodes | Sanctuaries | POBH - ASIC Resistant | 10% ORPHANS
by
fjavi
on 30/04/2018, 20:30:31 UTC

That being said, when I look at Lich's explorer, a reindex may or may not be the explanation. I agree that the lower block number displayed indicates a partial index, but with a total supply of 0 and a price of 0, it could be something else is down. The hash rate is there, so the wallet is probably running, but depending on how he configured the total supply column, a reindex MIGHT be the explanation for the 0 there. As for the price of 0, I don't know if he ever had the C-CEX API configured to return a price...

It's reindexing, but it shows partial data because Iquidus proactively adds unknown TXs when a block number or hash is queried.

Quote from: capulo
75% is ok because if somebody has 1.5m for masternode, then he will build it. does not make sense to keep 1.5m in wallet

It still makes sense, because 1,5M BBP is enought to stake for 70K RAC, and that's about 11K BBP a day as of today, which is more than what a Sanc is giving now (unless mining costs "eats" the difference, of course)

This stalking debate is going to be always the same: if 3 guys have let's say, 50% of power, they are going to get 50% of rewards whatever system we employ. And I think that having millions of BBP "locked" down is economically harmful for them, but only if they have to pay their bills. Of course if we are talking about rogues and botnets, this stalking parameter is not going to stop them, because they have no penalty for having all that dough locked down.
Post
Topic
Board Announcements (Altcoins)
Re: BiblePay | Masternodes | Sanctuaries | POBH - ASIC Resistant | 10% ORPHANS
by
fjavi
on 27/04/2018, 21:24:39 UTC
In this week's list for delisted coins in C-Cex due to lack of volume I see Gridcoin, the one that competes with us in R@H.

True, but I see that Gridcoins Daily Exchange volume is $175,432 on the other exchanges, so whatever you are implying about our highest competitor being feeble is FUD.

Apparently all that is happening is people prefer to trade GRC on other exchanges.


No second intentions, I knew GRC was in C-Cex for long so this caught my eye. But it's logical that if they move along to bigger exchanges, the smaller ones see liquidity fly.
Post
Topic
Board Announcements (Altcoins)
Re: BiblePay | Masternodes | Sanctuaries | POBH - ASIC Resistant | 10% ORPHANS
by
fjavi
on 27/04/2018, 12:59:05 UTC
I don't know if it's related to today's special situation with the superblock and PoDC, but blocks interval seems to be way higher (about 12 mins each on average)...
Post
Topic
Board Announcements (Altcoins)
Re: BiblePay | Masternodes | Sanctuaries | POBH - ASIC Resistant | 10% ORPHANS
by
fjavi
on 27/04/2018, 12:49:42 UTC
It was sent from c-cex by txid 3190dfb16af1d7b3acef01e1234cb7a5772e519ec24732074b4e0d9e8a71eac2 into BNxpNcfZDzGknyqguVh2anPKae2jrAfGxH

and then via txid d72cb76f612698b96c3057b5b1f553c17d93f8eb07b85664cebd973549de2140 into two wallet addresses. Now the amount via bbp explorer (BQGcjqjbx89DYqtHc9MpubeEBnbb9FPyfg) is not corresponding with the total balance i see in the wallet.

The wallet will show you the sum of the balance of all addresses used by the wallet.

You will understand it better by enabling "Settings->Options->Wallet-> Activate coin control feature checkbox". Then you go to "Send" tab and press the blue button "Inputs...". There you will see in which adresses the different amounts are kept. That should match 100% with the info you see in block explorer.
Post
Topic
Board Announcements (Altcoins)
Re: BiblePay | Masternodes | Sanctuaries | POBH - ASIC Resistant | 10% ORPHANS
by
fjavi
on 27/04/2018, 11:56:21 UTC
I have one question regarding payment I dont understand.

Day before yesterday morning I sent 520k BBP from C-cex onto address BNxpNcfZDzGknyqguVh2anPKae2jrAfGxH (TXID is d72cb76f612698b96c3057b5b1f553c17d93f8eb07b85664cebd973549de2140)

When I take a look via BBP explorer on the main wallet address BQGcjqjbx89DYqtHc9MpubeEBnbb9FPyfg (address for the same wallet) I don't see +520k. I just see there some + 170968, rest of the transaction goes to another address.

Result: the final balance checked via BBP explorer on the main address BQGcjqjbx89DYqtHc9MpubeEBnbb9FPyfg (2863625) doesn't match now with the balance in the wallet (more than 3.2 mil.)

Question: how it works when I have more addresses for one wallet? And how can I check the final balance via BBP explorer?

I will appreciate any answer. Thank you.

The mentioned transaction shows that there are 2 inputs:

BQGcjqjbx89DYqtHc9MpubeEBnbb9FPyfg   2701763.00000000
BNxpNcfZDzGknyqguVh2anPKae2jrAfGxH   519999.90000000

And 2 outputs:

BRjWGBbhAvwuVcXpWkhYFkwRU2V3mR9CgL   349031.89910260
BQGcjqjbx89DYqtHc9MpubeEBnbb9FPyfg   2872731.00000000

So properly speaking, this is not the one you are describing, as BNxpNcfZDzGknyqguVh2anPKae2jrAfGxH is not a receiving address, but one of the two "sending" addresses.

Regarding the wallet behaviour: unless you specify a "change" address explicitly, wallets will create a new address for change every transaction.

Post
Topic
Board Announcements (Altcoins)
Re: BiblePay | Masternodes | Sanctuaries | POBH - ASIC Resistant | 10% ORPHANS
by
fjavi
on 27/04/2018, 06:52:01 UTC
In this week's list for delisted coins in C-Cex due to lack of volume I see Gridcoin, the one that competes with us in R@H.
Post
Topic
Board Announcements (Altcoins)
Re: BiblePay | Masternodes | Sanctuaries | POBH - ASIC Resistant | 10% ORPHANS
by
fjavi
on 26/04/2018, 13:08:41 UTC
I'm trying to start a masternode, but the mnsync seems to stall on 'MASTERNODE_SYNC_GOVERNANCE'? Blockchain is synced, 8 connected peers, wallet is 1.1.2.4. I tried a reindex, but that didn't help. I also installed watchman, but that needs a synced mnsync.



The same happened to me yesterday. For some reason I rebooted the machine and biblepay daemon and it synced fine, still it took several minutes to do it.
Post
Topic
Board Announcements (Altcoins)
Re: BiblePay | Masternodes | Sanctuaries | POBH - ASIC Resistant | 10% ORPHANS
by
fjavi
on 26/04/2018, 10:50:04 UTC
Hi,

I dont know whats going on but I had this morning "No sync..." situation, so I updated client from 1.1.2.3 to 1.1.2.4 and deleted blocks, chainstate, mn*.dat , governance.dat, banlist.dat.
I had 15000 immature coins on the wallet from mining, now, i dont have them anymore, only few coins from way back(several months ago).
Can anyone help?

Please post your mining address to check if those 15000 BBP are in the latest PoDC distribution in the main chain.
Post
Topic
Board Announcements (Altcoins)
Re: BiblePay | Masternodes | Sanctuaries | POBH - ASIC Resistant | 10% ORPHANS
by
fjavi
on 24/04/2018, 14:12:55 UTC
every new user/miner add these nodes to config with peerers problem


addnode=node.biblepay.org:40000
addnode=biblepay.inspect.network  
addnode=node.biblepay-explorer.org


Don't recommend this, the second and third node are both dead, and the first node line isn't needed, it's already hard coded in the wallet.

For syncing issues, I would try going to the last pages of http://explorer.biblepay.org:3001/network , finding 1.1.2.1+ IP addresses and then in the console window type:
Code:
addnode "x.x.x.x:x" "onetry"

The problem with the node.biblepay.org being the master,  it is contributing to the sync/crash issues.

Since it was down, many users were unable to use the client.   this is a huge centralization issue

Lesson: if you want to take down bbp only go after 1 node.

This would only affect new nodes. After a node connects for the first time, it keeps a list of possible peers so even if the original master is down it can keep on working.

And this is not a "problem" of BBP, it happens with all Bitcoin-like coins.