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

Pages: 1 2 3 4 5 6 [7] 8 9 10 11
91
Pre-Proposal Discussion / Re: Mass Adoption for BiblePay II
« on: December 04, 2018, 02:24:59 pm »
My only concern with using it on the POBH side is it directly competes with PODC..

PODC combines coins into one for the updates, so only folks not working on PODC could participate in POG, this would need to be addressed somehow.

92
General Discussion / Re: Kairos Children's Fund: Call for sponsors
« on: December 03, 2018, 05:31:13 am »
The site doesn't seem to load.

We're grateful we have been able to support the children!  Thanks for organizing your part as well!

93
Pre-Proposal Discussion / Re: Payment Gateway offer
« on: December 03, 2018, 05:29:23 am »
Looking over the main site is painful,  (mainly due to the sweeping text css on every paragraph) haha.

But they seem to only have been around a few weeks.

They require their coins: https://wallet.crypto-bridge.org/market/BRIDGE.CUX_BRIDGE.BTC
has been active on cryptobridge for a month (we're no longer active there if I recall correctly.

Theis ANN:
https://bitcointalk.org/index.php?topic=5059258.0


Overall the concept is the direction we want to head, but its basically investing a LOT into an ICO at this point.

It's interesting, there is a bribe in the  ANN to recruit coin devs,  and this site + the mn site are one and the same

94
Pre-Proposal Discussion / Re: MNCOINNEWS offer
« on: December 03, 2018, 05:18:59 am »
There are so many of these sites currently,  it's hard to imagine any of the new ones will be seen..

Kind of reminds me of the early 2000's pixel advertising fad

It's interesting, there is a bribe in the  ANN to recruit coin devs,  and this site + the debit card site are one and the same

95
Pre-Proposal Discussion / Re: Add Proof-of-Giving
« on: December 02, 2018, 07:26:33 pm »
My thought was running two coins.  Since the new concept is so different from what is currently working, launching it from scratch made the most sense to me.  That would give two options -- one for the more advanced users and the other that is so easy to use, anyone, can set it up.  I don't see any way to have such a significant fundamental shift without massive devaluation. 

Most of us probably mine multiple coins already, so if doing the other system on my cell was easy, I would do it.  If you focus the marketing nearly exclusively on mobile devices, it shouldn’t be a direct competitor for the current BBP system.

Without more people to pick it up,  a fork like that would split already limited resources..  Plus would be difficult to get on to any exchanges at this point.

Not a bad idea overall,  but I don't see it workable in the short-term.

96
Pre-Proposal Discussion / Re: Add Proof-of-Giving
« on: December 01, 2018, 05:25:42 pm »
I didn't see anyone else ask this, so I apologize if this is redundant, but what about doing a fork and running with the current system and POG?

hard fork, or branching fork?

I don't see people wanting to run 2 chains,  and any other change would require a hard fork

97
Pre-Proposal Discussion / Re: Add Proof-of-Giving
« on: November 29, 2018, 10:50:23 am »
For future investigation - a potential end-to-end solution for POG:

1.  POG Difficulty algorithm dynamically gyrates from .01 - 65535
2.  Difficulty dictates minimum_coin_age, minimum_coin_amount, and maximum_tithe_amount accepted inside POG stake
3.  The coin staked must be greater in value than the tithe amount (IE the staked coin is used to pay the tithe) and the tithe must be staked by one coin only
4.  POG Difficulty regulates the maximum tithes per month to be accepted (approx 4 million max tithes per month decreasing at the current deflation rate)
5.  Remove uncertainty principle, make pool rewards certain again
6.  Add a tithe helper dialog that shows  the individual max tithe amount based on all owned coins (or a label)

Pros:

1.  Can not be scripted to be exploited based on time of profitability
2.  Pool will not collect more than the max tithe amount per month (preventing dilution)
3.  Does not directly make the rich richer (as the individual coin is a random cross section of BiblePay) - in contrast to POS (where the highest coin_amount*age stakes the most coins and money)

All credit to Yeshua.

Interesting, this would alleviate some of the "too much to dump" issues,  I suppose the monthly budget could be used to "fill the gap" between the tithe and the required orphan funds.

#3: The coin staked must be greater in value than the tithe amount (IE the staked coin is used to pay the tithe) and the tithe must be staked by one coin only

I'm not understanding the "tithe must be staked by one coin only" part, could you elaborate?


I'd need more info on the pool rewards,  (how they are calculated / split,  will it be like now where POW(POBH) is somewhat "random", and would get harder as difficulty increases)

98
Pre-Proposal Discussion / Re: Trust level of Proof-of-orphan-mining
« on: November 29, 2018, 07:49:08 am »
Thanks for the feedback guys, I added a second no option.

99
Pre-Proposal Discussion / Re: Trust level of Proof-of-orphan-mining
« on: November 28, 2018, 02:37:00 pm »
I'm voting for the API ...

Personally, I'd rather pay for another orphan than for a PO box. :)

100
If he has 3 machines with a cloned wallet, and only one is showing the cpid for 'exec getboincinfo', I recommend checking these two things:

1) First ensure the other two nodes are synced:


getblockhash 85400
Yields:
c1f836bdb2318b26b9a954c0258b131f90726fdc4d34d17bbc21a398dedd5abf


2) If that doesn't work try this from the non-working nodes:
cd ~/.biblepaycore/SAN
rm prayers_prod
Restart wallet
(then try the exec getboincinfo again)


(Its rare, but I've seen the prayers file corrupted before, that is the file that stores the cpid info.  More specifically, I believe it could be corrupted if there is a permissions issue on the machine - say the user isnt granting access to the SAN directory for example.  )

Rob

Good information i'll keep this handy!

101
Looks like your windows and mac wallets are different than the main wallet.

I would copy the main wallet.dat to the other machines (make a backup first just in case)


102
Something still is not adding up

run this on each client.
getaccountaddress ""

Make sure all the addresses are the same.

103
Looking up your CPID you are receiving payments...
I see 3 machines attached to that CPID.

Do you have the wallet copied from the main machine to the others?

https://forum.biblepay.org/tools/podcstatus.php?cpid=83f33d4a5e046be370ffc4dd5378fad9

104
Unfortunately I have.  The strange thing is when I put my info into the client and hit the diagnostics button, everything looks fine but the debugger shows the same issue.  Just to make sure, I tried to associate again and got the warning Already_In_Chain.

Could you post or PM me your CPID? I'd like to check the chain data.

You could also do a "exec associate <username> <password> true" to force it to re-announce.

105
Pre-Proposal Discussion / Re: Add Proof-of-Giving
« on: November 24, 2018, 06:18:49 pm »
Couple of questions:
How would this handle multiple-client/machine miners (one large wallet, but copied to multiple machines for mining purposes)? 

What happens if we get over 1k miners,  the reward and/or chance would drop drastically, 

Would there be logic to prevent someone from missing too many payments (or getting paid too many times, while others "Starve")

It's an ambitious proposal.. .


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