Bible Pay

Recent Posts

Pages: 1 2 3 [4] 5 6 7 8 9 10
31
Production Proposals / Re: PRE-PROPOSAL - Advertising - Google Adwords
« Last post by LifeThruGrace on July 03, 2018, 11:11:30 pm »
I think another angle could be retirement, recurring income (via masternodes), charity, bible, biblical... I think there is some opportunity here to obfuscate the crypto technology part while amplifying the charity aspect. It has to be done in a safe, transparent way though... so we don't come off a sheisters...
32
Production Proposals / Re: PRE-PROPOSAL - Advertising - Google Adwords
« Last post by togoshigekata on July 03, 2018, 01:37:32 pm »
I freshened up the Facebook page,
and now Im testing my first ad,
"boosting" a post I made, for $25 should reach 12-83k users,
right now the ad is "in review"

UPDATE: My ad was rejected lol
"For ads that promote cryptocurrency and related products and services, the advertiser must first receive our prior written permission. You can apply to become an eligible Cryptocurrency and Related Products and Services advertiser. We also recommend that you have a look at our Cryptocurrency Products and Services policy for more details."

Cryptocurrency Products and Services Onboarding Request
https://www.facebook.com/help/contact/532535307141067

I submitted a request
33
This was in testnet, on v1.1.3.7.
Looks like its up to 21MB already hmmm

Im seeing a ton of this message:

ProcessBlockFound: Generated: ######
CPID has solved prior blocks. Contextual check block failed. CPID ######### ERROR: ProcessnewBlock: AcceptBlock FAILED
PrcoessBlockFound -- ProcessNewBlock() failed, block not accepeted
CBlock(hash= **** CTransaction ** CtxIn ** CTxOut

Maybe its because of too small amount of miners in testnet?

Hmmm I accidentally put a $ symbol in front of debugmaster=true instead of a hashtag to turn it off, I wonder what that did

Try removing or renaming debugmaster=true.  The parser probably interpreted that wrong.

Im using 231K on linux and 269K on windows in Prod on 1138 after running for a half hour and being fully synced.

21 Meg means something is really wrong on the node.  Could be those settings...

My log is clean now but I did release a small patch, but it only removed 2 messages.

34
This was in testnet, on v1.1.3.7.
Looks like its up to 21MB already hmmm

Im seeing a ton of this message:

ProcessBlockFound: Generated: ######
CPID has solved prior blocks. Contextual check block failed. CPID ######### ERROR: ProcessnewBlock: AcceptBlock FAILED
PrcoessBlockFound -- ProcessNewBlock() failed, block not accepeted
CBlock(hash= **** CTransaction ** CtxIn ** CTxOut

Maybe its because of too small amount of miners in testnet?

Hmmm I accidentally put a $ symbol in front of debugmaster=true instead of a hashtag to turn it off, I wonder what that did
35
My debug.log got filled up, I think its from leaving debug=true and debugmaster=true on for all this time, saved last 100 lines of log and removed it and commented out the config options

Only in testnet, or in prod?

EDIT: Ill run two nodes in prod on 1138 and see if something should be done if so we can rerelease a patch.

EDIT:  Is there anything in your saved file we should remove?
36
TheSnat, could you please see if you introduced this bug with the PODC filters?

https://github.com/biblepay/biblepay/issues/28

Oddly I'm not seeing this on all my wallets, only a few i'm trying to figure out why.
37
My debug.log got filled up, I think its from leaving debug=true and debugmaster=true on for all this time, saved last 100 lines of log and removed it and commented out the config options
38
TheSnat, could you please see if you introduced this bug with the PODC filters?

https://github.com/biblepay/biblepay/issues/28

39
Updated to v1.1.3.7

left it running for a few hours, mnsync status  was stuck syncing, I was worried I was on a fork,
so I did a clean and reindex, mnsync status is still stuck syncing,
my masternode shows as Missing,
so I enabled it again and its in PRE_ENABLED state

getblockhash 46512
6268ef875***ea90589

My hash matches.. let me do some sanc testing to make sure we are emitting PODC superblocks.

40
Updated to v1.1.3.7

left it running for a few hours, mnsync status  was stuck syncing, I was worried I was on a fork,
so I did a clean and reindex, mnsync status is still stuck syncing,
my masternode shows as Missing,
so I enabled it again and its in PRE_ENABLED state

getblockhash 46512
6268ef875***ea90589
Pages: 1 2 3 [4] 5 6 7 8 9 10