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

Pages: 1 2 3 4 [5] 6 7 8 9 10 11 12 ... 32
we also should be testing the auto unlock password;
ensure you can mine with a locked encrypted wallet, and ensure you can send a gscc also.

I clicked Settings >> Encrypt Wallet

"getmininginfo" shows hashps

I tried to do "exec sendgscc true"
but I got message "Diary entry incomplete. (code -1)"

Looks like I went on a lone fork, I reindexed and Im back in agreement

Upgraded to v1.4.2.2b


Yeah on the anonymous talk, I think its important for fungibility to have anonymity,
I also think its important for personal safety,
I think in the much much past you may have been open to disable PrivateSend?,
but it sounds like you may now lean more towards privacy/anonymity?

Also, I noticed in the evo docs theres a section about Tor

Casa Node just added a Tor update

I really dont know much of anything about Tor,
Ive heard rumors/stories that most of the exit nodes have been compromised,
but anyways Id be open to testing it out for BiblePay

Thank you for answering all my questions Rob!

do you have blockhash 06af* for 52240? 
Also whats your IP for your sanc, Id like to see if it shows in my enabled list.
(You see 4 enabled in your sanc list correct)?
Are you in the leaderboard yet Togo, as I only have 5 participants there?

Im in agreement on blockhash for 52240
My masternode IP is:
I see 4 ENABLED masternodes

I never registered my cpk, so I just ran "exec cpk togo"

How do you view the leaderboard?
"exec prominence" is not working for me "Command not found"

Also do I need to run "exec join pog"?
Are POG and ABN different things?

Awesome, Thanks Rob!
Thank you for all of your hard work!
This is exciting!

Sorry for providing too little information about the Watchman environment; let me try to explain.

In Prod, we are running a 1.5 year old codebase with Dashs Sentinel in Python (we renamed it Watchman-on-the-wall) - and we still use it in prod as-is from Dash (and its still required today since it helps create the budgets etc, creates watchdogs, etc).

In Evo, I have not ported Sentinel to Watchman yet (so its unavailable still), so we do not have to Test it yet.

What I'm considering however, is porting Watchman to c++, so we don't have to run both watchman and Evo as separate programs in each sanc (in the future).  (Thats what this release info was about, but - its really just in step 1).  I'm still going to do some internal testing on my end, then provide more info as how we can test the integrated version of watchman, so please don't worry about testing that yet.

Ive tried to make masternode again now with 4500001 tBBP,
I was able to add it to masternode.conf and start it!

Now I just need to setup Watchman?


Also I got a popup message about masternodeblsprivkey
"BiblePay Core - Warning - You should specify a masternodeblsprivkey in the configuration. Please see documentation for help."

Im kind of confused how the bls keypair works

"The ProRegTx contains 2 Dash addresses (also called public keys) and one BLS public key, which represent 3 different roles in the masternode and define update and voting rights. The keys are:

ownerKeyAddr: This is a Dash address (public key) controlled by the masternode owner. It is different from the address used for the collateral. Because the owner uses the private key associated with this address to issue :ref:`ProUpRegTx <update-dip3-config>` transactions, it must be unique for each masternode.

operatorPubKey: This is the BLS public key of the masternode operator. Only the operator is allowed to issue :ref:`ProUpServTx <update-dip3-config>` transactions. Because the operator key is used during live masternode operation to sign masternode-related P2P messages, quorum-related messages and governance trigger votes, the BLS key must be unique for each masternode.

votingKeyAddr: This is a Dash address (public key) used for proposal voting. Votes signed with the corresponding private key are valid while the masternode is in the registered set."


Masternode Setup:

These are my old Masternode setup notes:

Attempt to use VNC:

Masternode guide:

Thanks for looking into things Rob!


On a side note, the only change back to the CPK should be coming from those ABN/GSC transactions, when we create an ABN/GSC stake, we send the change back to the CPK. 

1. So this coin splitting behavior is intended and happens automatically every so often? when mining? (and every wallet is now set to mine by default?)
1.a. Is an amount of 4500001 ignored for coin splitting? when user is setting up a masternode?
1.b. Does this mean new miners have to own some amount of BBP coins in their wallet to participate in mining? (but they can jump in to mine when block hasnt been solved for 60 minutes if they dont have coins?)

2. Also for the CPK, I noticed that I never ran a command (exec cpk my_nickname) to create one, is default behavior that one is created automatically? And the command is to just add a nickname to it?


Just poking around the documentation:

GSC (Generic Smart Contract)
"The GSC is split into a client server architecture. The client side user joins campaigns with a CPK (Christian Public Keypair) and competes in these campaigns for points. The server side (our Sanctuaries) assess user points and tracks user progress. Once per day, the points are converted and paid in a Generic Smart Contract. The GSC is voted on by the Sanctuaries automatically at a certain chain height. The GSC is paid once per day as a superblock from BiblePay core, and is split among campaigns by points rewarded per campaign per user. "

ABN (Anti-BotNet)
"which requires a certain amount of coin*age to be present in each mined block in order to mine BiblePay"
"Our network requires an average calculated and pre-assessed static amount (posted in getmininginfo) of required coin*age and stores this in the chain. Each miner checks this number, and will search the wallet (this is all automatic) for coins totaling the requirement and place these coins in an ABN Stake transaction - and then begin mining"


3. Is the ABN Stake transaction just coins going to the CPK address?
3.a. I havent noticed any of the CPK address transactions in my Transactions list, filter set to All, but I do notice coins moving around in Send >> Inputs (Settings >> Options >> Wallet >> Enable coin control features)

I've been trying to start a Sanctuary, but I can't seem to sync my wallets properly :(

rm blocks -r
rm chainstate -r
rm evodb -r
rm SAN -R
rm gov*
rm mnc*
rm mnp*

I just delete everything other than the wallet.dat, backups folder, biblepay.conf, peers list and masternode.conf

And then I do a ./biblepayd -dameon -reindex

Hmm it happened again, got screenshots:
looks like coins get split up into the "CHRISTIAN-PUBLIC-KEY" address automatically

Im attempting to setup a masternode now

I was trying to do it by command line but sent coins to wrong address,
so now I installed lubuntu and am trying again


These are my old notes:

Attempt to use VNC:

Masternode guide:


I get nothing back when typing masternode outputs,
then I tried checking the balance of the address (getbalance) I sent to and it was 0,
I turned on coin control and checked, and it seems almost all the coins are in a "(change)" address

Ill try again

I also noticed there was an additional 10% Foundation tithe added on to the initial transaction, even though I didnt click any checkboxes in the GUI

Upgraded to v1.4.2.1b

Code: [Select]
./biblepay-cli getblockhash 48789

Thanks Rob! I have about 7.9 million tBBP now, Ill set up a masternode soon

Upgraded to v1.4.2

I confirm same hash for 42424

Code: [Select]
./biblepay-cli getblockhash 42424

Im currently at:

Code: [Select]
./biblepay-cli getblockhash 43157

Pages: 1 2 3 4 [5] 6 7 8 9 10 11 12 ... 32