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

Pages: 1 2 [3] 4 5 6 7 8 9 10 ... 17
31
Actually if you are on 1.4.8.2, double check that, then delete 'instantsend.dat' and restart, and let us know?

Let me know if it still re-hangs.

it's the latest version I compiled myself. I tried to delete bnstantsend.dat and rescan but still at 17444.

32
I am trying to sync testnet but I am stuck at block 17444. I see many peers so I don't know how to get it updated.
I will try to rescan and come back when ready

33
Archived Proposals / [MIP] Oct-Nov 2019 payroll
« on: November 20, 2019, 08:31:08 AM »
Hi all

I would like to kindly ask some compensation for Oct/Nov 2019 support/development tasks

Evo binary compiles for Linux x64 & ARM and MacOS, mainnet and testnet
User support in discord/email/other channels.
Mobile wallet: bug chasing crash in iOS due to SPV receiving corrupt flagLen data.
Other research tasks related to pool, MacOS specific, POBH 2.0, Dash 0.14 codebase merge.
Dealing with several service providers offerings in discord.

In all a capped amount of 2M.

Thank you very much!

34
Does anyone have an IP to use in addnode for this testnet? seems the one I had from past test is no longer valid.
Thanks.

35
Archived Proposals / Re: BiblePay Evolution 2.0 Changes for Future Growth
« on: October 20, 2019, 04:03:13 PM »
I fully agree with each and all of the proposed items.

Great analysis and great work as usual, thank you Rob!

36
Archived Proposals / [MIP] Aug-Sep compensation
« on: September 12, 2019, 11:18:35 AM »
Hi all

I would like to kindly ask some compensation for Aug&Sep 2019 support/development tasks

Evo binary compiles for Linux x64 & ARM and MacOS, mainnet and testnet: 1h
User support in discord/email/other channels: 4h
Mobile wallet sync problem solving: 4h
Debug/fix -reindex crash: 8h
Follow up with Apollon and Satoshisolutions: 3h

In all 1000€ (2.150,000 BBP), capped to 1,200,000 (1,2M) BBP

Thank you very much

37
I believe Im the only 2 sancs left; MIP & Oncoapop are you guys still participating?

Jaap said he would, but we havent heard back from him after that.  I havent seen Togo here either despite coming back on the payroll.

I switched off mine in the Vultr VPS. I made a snapshot so maybe I can take it back again.

Apart from that, what else do you need from me to test?

38
Archived Proposals / Listing in MN hosting SatoshiSolutions
« on: August 26, 2019, 02:19:11 AM »
I requested a listing in SatoshiSolutions, and advanced a $250 fee myself, by selling 540000 BBP from my sanc.

Regarding the listing itself, it seems that we caught them in the middle of a merger/swap with other project, and to add up, in the middle of a migration to an improved infrastructure for MN hosting.

I told them I understand the circumstances but if they can provide a deadline for the listing, this will give more visibility to the community.

I have also spent a few hours contacting them to help compile the new wallet, but I will leave the proposal as it is to recover the advanced fee.

540000 BBP

Thank you very much

39
Archived Proposals / Re: Aug 2019 - Block reward breakdown adjustment
« on: August 13, 2019, 04:14:53 AM »
For some reason I cannot edit posts (not even OP)

But yes, I do agree with your proposed reward distribution
20% - Charity and Governance
25% - GSC
35% - Sanctuary budget
20% - POBH/Security

I also agree that, if approved, it must be deployed whenever is best for the coin's interest, not immediately.

40
Archived Proposals / Aug 2019 - Block reward breakdown adjustment
« on: August 04, 2019, 11:47:41 AM »
With the new GSC system that came as an exciting novelty in Biblepay Evolution codebase, the block reward breakdown was substantially changed to

GSC 40%
PoBH 20%
Masternodes 20%

(remaining 20% consists of Charity/IT/PR monthly superblock)
 
I believe that this breakdown strongly discourages MN owners and gives incentive to dismantle MNs and bet for the bigger ROI of GSC.

While we all will benefit from the inflow of new users that GSC brings, at this moment GSC is reported to be 10-12 times more profitable than MNs.

Also, Masternodes operation has associated costs and burdens, and in the near future MNs will have a key role in maintaining the network integrity with LLMQ.

Because of this I would like to propose a more balanced reward breakdown of:

GSC 30%
PoBH 20%
Masternodes 30%


This still leaves GSC room to grow, without eroding too much the original promise of 40% reward for MN owners.

PoBH remains untouched as I believe it's critical for the integrity and the added value of Biblepay chain.


41
In my case it was not the masternodeblsprivkey (but that is still the most common cause of POSE bans).
In my case I had the externalip= set (to the correct IP) but for some reason the other nodes didnt like that, so I recreated my sanc. (without an externalip).

Now Im back in the list with 0 pose ban.

Im interested in seeing who else gets POSE banned.

LLMQ is enabled now.

MIP do you have a sanc also?  I know Oncoapop just added one so we should have 5 total if MIP has one.

I had one, I just updated but I think I may be in the wrong chain, I will resync.

42

So lets go back to Testnet for a while, and once we enable the dip3 sancs in mainnet, Ill jump in testnet and try to mine for a day or two and join you guys and see if we stay on track.

As you both might know, 1.4.5.9 has no sancs to load gov data from either (from mainnet), so its probably banning sancs too.

Ok understood. Tell us if you need to check anything else in testnet.

43
I reindexed and everything seems fine. I am with funded mining. I will leave it for a while then try unfunded (unless you instruct me otherwise)

44
I am trying to test pool mining, but after 15 minutes the Core client is stuck in “Connecting to peers” and it does not sync. I just set up:

pool=https://pool.biblepay.org
workerid=MIP
minersleep=0
generate=1

There are 20 banned peers and around 10 working ones too.
I will wait a few more minutes to see if it fixes

PS: I see this in debug.log
Code: [Select]
2019-07-19 19:07:26 ERROR: AcceptBlockHeader: block 6e6f1676585e16959bb1dc81fcc79a60932ee29cd8681504f4295a97547fd92b is marked invalid
2019-07-19 19:07:26 ERROR: invalid header received
2019-07-19 19:07:26 ProcessMessages(headers, 26409 bytes) FAILED peer=0
2019-07-19 19:07:32 ERROR: AcceptBlockHeader: block 6e6f1676585e16959bb1dc81fcc79a60932ee29cd8681504f4295a97547fd92b is marked invalid
2019-07-19 19:07:32 ERROR: invalid header received
2019-07-19 19:07:32 ProcessMessages(headers, 26409 bytes) FAILED peer=1
2019-07-19 19:07:35 Loading addresses from DNS seeds (could take a while)
2019-07-19 19:07:35 1 addresses found from DNS seeds
2019-07-19 19:07:35 dnsseed thread exit
2019-07-19 19:10:13 ERROR: AcceptBlockHeader: block 6e6f1676585e16959bb1dc81fcc79a60932ee29cd8681504f4295a97547fd92b is marked invalid
2019-07-19 19:10:13 ERROR: invalid header received
2019-07-19 19:10:13 ProcessMessages(headers, 26409 bytes) FAILED peer=1
2019-07-19 19:18:02 ERROR: AcceptBlockHeader: block 6e6f1676585e16959bb1dc81fcc79a60932ee29cd8681504f4295a97547fd92b is marked invalid
2019-07-19 19:18:02 ERROR: invalid header received
2019-07-19 19:18:02 ProcessMessages(headers, 26490 bytes) FAILED peer=1
2019-07-19 19:22:32 Timeout downloading headers from peer=1, disconnecting
2019-07-19 19:22:33 ERROR: AcceptBlockHeader: block 6e6f1676585e16959bb1dc81fcc79a60932ee29cd8681504f4295a97547fd92b is marked invalid
2019-07-19 19:22:33 ERROR: invalid header received
2019-07-19 19:22:33 ProcessMessages(headers, 26571 bytes) FAILED peer=2

The only thing I've been doing in this Mac lately is solo mining.

45

Can you try it all over again, and see what the total lag is?  Also could you check the log and see what the timestamp difference is and how long it took to recover?

This way we can modify the code to remove that situation.

Also, you didn't explain if it was a locked wallet; was it because the wallet was locked and then you unlocked it and the problem goes away after a certain amount of time?  (The error in the log would be telling).

I wonder if we should design the wallet to be able to mine without being unlocked.  Maybe this is a hurdle for newbies.

Again, is this 1.4.5.9 that is being tested (cause I think 1.2 in prod was a few months ago).




I am on 1.4.5.9 against mainnet
The wallet was locked but I unlocked and this message was there for several hours after unlocking.
However I repeated the same steps now and I can't reproduce the same message, it behaves as normal.

So maybe it was a glitch on my end.

About unlocking the wallet, I think it would be user friendly to detect that user has setgenerate=true and then, if wallet is locked, show some red message on the Overview screen to unlock it.

Pages: 1 2 [3] 4 5 6 7 8 9 10 ... 17