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 - Rob Andrews

Pages: 1 ... 110 111 112 113 114 115 116 [117] 118 119 120 121 122 123 124 ... 263
1741
Ok, please go ahead and start testing again.

I will explain the changes to help mobile accessibility asap.

So this is a 'tad' bit convoluted but I will be improving the SSO flow asap, but for now here is how you log in:

Click "Log In".  From the forum, after you log in, click "FOUNDATION" which is on the left menu.

Of course you don't need to be logged in for most of the pages, but for posting data, etc.

(The primary thing missing is we should redirect you back to the foundation.biblepay.org if you came from there and logged in).


One other tidbit of info for mobile devices:
You have to click the top right menu-show icon to see the left menu if the width of the screen is below the mobile threshhold - to see the menu, etc.  This is pretty self-explanatory already.




1742
Hi All,

Let me look into all these issues now.

Ok, please go ahead and start testing again.

I will explain the changes to help mobile accessibility asap.





1743
Hi All,

Let me look into all these issues now.

1744
TestNet Discussion Archive / Re: BIBLEPAY - RANDOMX INTEGRATION
« on: March 07, 2020, 06:47:45 PM »
Test cases for DAC (1.5.0.5):

Please primarily test all these below in QT mode.  Since a lot of changes rely on graphics.

So the way this dual-branded release works is the core wallet will detect the name of the program being launched, for instance if you launch dac-qt, it realizes it is DAC.  If you launch biblepay-qt, it realizes its BBP.

If it is launched in DAC mode, you will see a different splash screen, the theme will be overridden to be DAC (and will not allow you to pick BBP themes), and everywhere in the wallet that used to say "BiblePay" should say "DAC".  Including sending coins, etc.  Please verify that is the case.

Also please launch the biblepay version and verify the old themes still work, Bezaleel still works and things still say biblepay.

The 'exec price' command should still provide the currency price (for the leaderboard).  The leaderboard should appear identical in both wallets (please check that).

To test the linux qt version, note the zip contains both 'dac-qt' and 'biblepay-qt'.  Testing those is straightforward, just run each one.
However in windows, we only released the biblepay version (due to a change that is required in the Microsoft installer for DAC.EXE, and we don't need to do that until we know the outcome of the future poll), so for now please install the windows version like normal, first test biblepay-qt.exe, then copy "biblepay-qt.exe" to "dac-qt.exe" in your windows directory, then test the DAC version.

The peers list should interoperate between the two versions, except, the DAC version advertises itself slightly different than the BBP version, but they see each other. 

The Sanctuaries list should be checked also.

By the way, in this latest release we fixed the toolbar icons for biblepay-qt (for windows and for linux).  They were not transparent now they should be transparent and fixed.

Also, just fyi, we just moved our github repo to this location: https://github.com/biblepay/biblepay/
But note:  we added an auto-redirect in from /biblepay-evolution to the new location so this means your build scripts should not really need to be updated.  (For develop or master).


1745
TestNet Discussion Archive / Re: BIBLEPAY - RANDOMX INTEGRATION
« on: March 07, 2020, 06:40:42 PM »
BiblePay - DAC
1.5.0.5 - Leisure Upgrade for TestNet

- Add DAC theme, DAC Splash, DAC currency_name, DAC Github, DAC icons and images
- Add ability for wallet to pick up on startup environment program name (If DAC, theme as DAC, if BiblePay theme as BBP themes)
- Add RandomX Spork Enforcement rule

** Please use this link for Linux binaries : Linux 64 bits II (QT/biblepayd/biblepay-cli) zip:  https://biblepay.org/bbp-lin-develop-64.zip
Or, use the windows64 link in the op post for windows **


1746
TestNet Discussion Archive / Re: BIBLEPAY - RANDOMX INTEGRATION
« on: March 07, 2020, 05:42:10 PM »
I have been thinking, perhaps you could add tls for monero as option in future release?

like if we set in parameters: 
Code: [Select]
--tls   we get sent to diffrent pool option.

Also if you could  differentiate bbp rejects and xmr rejects..
I have one cpu that has some invalid xmr shares that it probably shouldnt have.
So just figured for  troubleshooting purposes.

Hi Earl,

On part 1 of this:
https://xmrig.com/docs/proxy/tls

So, I'm not replying that we *cant* do it, but, instead, we just cant do it at this phase.  Here is why:  One, we have this nomp system running as a proof of concept.  Although I fully believe it will work (and probably scale), I dont want to modify nomp for TLS until we know it can handle the traffic load and does not need rewritten.  Another words, there are a couple growing pains we need to go through:  One is ensuring we dont have white hat hackers trying to circumvent the charity aspect too soon (even though we are adding the sporks first), we just may need to pull in the C version of Monero and stop using minexmr (I dont want to, Im just saying we have to keep this option open), and secondly, if nomp does not scale well, if for example if we have 2000 new XMR miners and we find nomp is sluggish, instead of adding second and third pool I might write DAC-XMR in c# again (now that I know more about stratum, and Monero).  So with these unknowns, its not worth adding TLS to nomp just yet.  So, again Im not saying no, Im just saying since all the pool traffic goes through nomp, it cant handle this yet.  Of course I will get HTTPS working on nomp first and maybe we can turn on SSL for mining first as a req baby step then revisit this after that works in prod.  We will have a github open then you can put in a new issue for this once SSL is working, cool?


1747
TestNet Discussion Archive / Re: BIBLEPAY - RANDOMX INTEGRATION
« on: March 07, 2020, 05:34:50 PM »
I have been thinking, perhaps you could add tls for monero as option in future release?

like if we set in parameters: 
Code: [Select]
--tls   we get sent to diffrent pool option.

Also if you could  differentiate bbp rejects and xmr rejects..
I have one cpu that has some invalid xmr shares that it probably shouldnt have.
So just figured for  troubleshooting purposes.

Hi Earl,

I havent looked into this yet, but on the second part about rejects could you please provide more info or an example, because to my knowledge, if you submit a rejected BBP share, our BBP rejects increase (as we know as the pool displays those in a separate column).
Now I havent been able to make a reject occur on the XMR side personally, but, to my knowledge the XMR rejects should increment separately and you should see those in the pool under the XMR column.

So could you provide more info, if this is something not happening in the pool or not happening in the xmrig, and if its in xmrig, what row is it missing on?
I dont need a screen shot just an example so we can pinpoint it.

Thanks.

1748
Hi,
I was looking on https://www.coingecko.com/ and tickers DAC or DEC are not available.
You have to look for others.
And for that name... Like you said, 3 words are very long name and 3 syllables will be better.
What about something like DArity?
But only available ticker for this name was ITY :)
It looks that almost all tickers are reserved :)
And to the rebranding. I like it. I like dual brand, but won't it be too complicated?
Rob, don't take it personally, but Biblepay sound too Christian.
I know, many of us are here due to that name and coin message, but it looks like there aren't many of us and we need a change to get more people.
How if it'll be working in dual brand? It will be still in one chain? I really dont see into this :)

Hi Orbis!

I'm not too worried if the ticker is taken, just as long there is no currency named "Digital Autonomous Currency" or "Digital Autonomous Charity" for example.
The hardest thing for us was getting a  3  character domain name and that was a challenge but we have those now.
We would have to make the ticker either an "X" or a 4 char ticker.  Such as "XDC" or "DACC" or whatever works, etc.

So yes I dont take it personally as I agree with you 100%.  Plus during the last year in spreading the gospel Ive realized that the ultimate situation is to bring non-Christians in anyway, as Jesus said we are to preach those that need the help, not to those that don't need a phsysician.  So bringing in 10,000 non Christians is the best thing we could ask for.

Anyway, I only thought of keeping the dual brand to have a gospel platform in the first place.  We can always retire biblepay and make a subdomain called gospel.dac.org, etc.  Thats probably a fine way to do it to.  Of course Im thinking yea maybe two brands will be the most confusing thing ever!  The original intent was to keep biblepay growing with ardent fervor and DAC growing simultaneously, but not if it adds net confusion.

To answer you question though if we did have dual brands, SX would give us two tickers pointing to the same order book.  We would have to have two web sites.  And two themes in the core wallet.  And two binaries.  But the underlying wallet would work the same.  Im making a wiki page on it, and if you come into testnet in a couple hours, after this upcoming release Ill walk you through it - as next release has a switch to run in DAC mode or BIBLEPAY mode.  (Technically speaking on boot, depending on mode you are in, the theme changes, the logos change, the name changes, the currency changes, the ticker changes, the price stays the same, and the leaderboard the same, the chain height the same and the same block chain, and the peers exist with a different prefix, but peers still work as normal peers across both wallets (IE they peer properly) ).

Just to clarify though, once it is compiled, if a user runs the dac-qt wallet, they don't see anything about Biblepay (the theme automatically switches to DAC).  If they run the biblepay-qt, they do see the biblepay themes.  So its not that confusing from the user side.




1749
TestNet Discussion Archive / Re: BIBLEPAY - RANDOMX INTEGRATION
« on: March 07, 2020, 01:26:51 PM »
I have been thinking, perhaps you could add tls for monero as option in future release?

like if we set in parameters: 
Code: [Select]
--tls   we get sent to diffrent pool option.

Also if you could  differentiate bbp rejects and xmr rejects..
I have one cpu that has some invalid xmr shares that it probably shouldnt have.
So just figured for  troubleshooting purposes.

I'll look into these two issues after we release; we are preparing a release for BBP & DAC now for testnet.


1750
I like that BiblePay is 3 syllables

10+ - Decentralized Autonomous Currency / Charity
10   - Digital Autonomous Currency
  7   - DECentralized Currency / Charity

I think a lot of popular brands are 2-4 syllables

Amazon, Nike, Apple, Google, Microsoft, Walmart, Facebook, etc

https://www.interbrand.com/best-brands/best-global-brands/2019/ranking/

===

Of the current options I like DEC - DEcentralized Charity the best
Interesting thought about syllables.

I also liked "DEC" the best (for the short name), as DEC is catchy.  People would say do you have any "DEC".
But one problem with DEC is I was only able to buy dec.app, and although that is a premium domain (google has something to do with that), Im not sure if it is as powerful as the NGO or ONG.

I'm still personally weighing the signifigance of Charity vs Currency.  (Not insinuating that my personal belief has anything to do with the outcome).

On one hand, Charity is clearer for our mission, you know you are getting a coin that has a humanitarian or altruistic purporse to help others.  However Charity is strong; and Im wondering if it leads a new investor to automatically think its a money pit (or not).  I am almost wondering if Decentralized or Digital Autonomus Currency will lead more general masses in (and be happy to find we do tithe , and have Christian principles later).  Or, should we be known as Digital Autonomous Charity right off the bat, etc.

Before you guys spoke up I was inclinging toward Digital Autonomous Currency simply because its a very generic and useful name, and we are tehcnically not hiding that we are charitable, but it begs to question should Charity actually be in our name.  This all comes from how much we pulled our price down (and of course with RandomX the hope is that is no longer an issue).  The theory is, if we are Currency, and the Charity part is not affecting our price, if we should be known as currency first and Charity in our details.

Im very, very suprised at how many already voted to just rebrand and ditch the biblepay name!  Its a little sorrowful, actually, but that will also be very interesting in the end to see if the supermajority (and I hope that is more than 75 voters!) vote to retire the biblepay name.

If that happens, Ill hold a second more granular vote to get more of an idea on the perplexity of the name.



1751
TestNet Discussion Archive / Re: BIBLEPAY - RANDOMX INTEGRATION
« on: March 06, 2020, 08:30:41 AM »
Dear Testers,

I would appreciate any help you can provide testing our new beta foundation website also:
https://forum.biblepay.org/index.php?topic=497.msg7053#msg7053

Thanks-

Will anyone be able to help out and test these features above?


EDIT:   Regarding corporate whitebranding, I'm adding it now; it's a huge change...  Hopefully we will have something to test within a couple days in testnet.

Edit 2: I am in the process of changing our github over to biblepay/biblepay (the way it was originally).  We will also move the data directory back to ~/.biblepay.  I know its a pain but I think for the longer term it will be clearer for everyone.  We can move away from "evolution" as that should have been considered a release (not a product) etc and I believe this has caused some confusion.


1752
Pre-Proposal Discussion / Vote on your favorite future currency name:
« on: March 05, 2020, 10:00:20 PM »
Biblepay is currently designing a future feature - the ability to offer corporate whitebranding.

In the process of doing this we are also considering offering a DUAL BRAND (One channel for users that are not necessarily Christians, for a Global reach).  This other brand would be our parent company (For example, we could be known as DAC.ngo, our name being DIGITAL AUTONOMOUS CURRENCY.  This brand would still tithe 10% to orphan-charity (with the exact parameters of BiblePay and would share BiblePay's codebase and exchanges).  But we would have two tickers:  DAC & BBP pointing to the same underlying order book.  We would also have dual block explorers, dual forums, and dual branded randomx pools.

Or, you may vote for one new brand only (retiring biblepay).  This will give us an idea of the general feel as to what name feels the best, and if users generally like the idea of a dual brand.

In addition to the potential dual brand, we plan on using the new DAC identity to launch our charity-agent feature.  For example, if we become known as DAC, our DAC foundation website will host the charity agent partner pages and deals by magnitude descending, while biblepay acts as a website for gospel media and preaching and salvation, etc.  Basically the DAC arm would be more aligned with those talking about crypto while the BiblePay brand would have more gospel features and media that might turn away some types of traffic (for example hell videos, etc).  However, we could work together to make subtle inroads into the DAC side to try to save those users.

So hence one of the reasons for the dual coexisting brand.  I am also consulting with SX to seek approval for dual-exchange tickers.



1753
TestNet Discussion Archive / Re: BIBLEPAY - RANDOMX INTEGRATION
« on: March 05, 2020, 09:16:49 AM »
BiblePay Core version 1.5.0.4 (64-bit) appears to hash on main chain

>getmininginfo

Code: [Select]
{
  "blocks": 180393,
  "currentblocksize": 1330,
  "currentblocktx": 1,
  "difficulty": 4694.69442578912,
  "errors": "",
  "pooledtx": 0,
  "chain": "main",
  "genproclimit": 4,
  "networkhashps": 537711.1247468939,
  "hashps": 3518.900343642611,
  "minerstarttime": "03-05-2020 09:41:24",
  "hashcounter": 1024,
  "pooledtx": 0,
  "chain": "main",
  "biblepay-generate": true
}


Thanks!

Thats good to know!

10-4 on the sanc info, the hashing and the syncing.  I think the speed is OK (I was looking at the sync speed in prod yesterday) - IE normal.


1754
TestNet Discussion Archive / Re: BIBLEPAY - RANDOMX INTEGRATION
« on: March 04, 2020, 01:00:38 PM »
For sure things arent as heated as back in 2016, the ethereum boom and all.

But should revenue go up for miners in comes alot of new people.

Also cpu mining are getting more and more folks intrested, for example monero switching to cpu friendly randomX .  And i belive some other algos also designed for cpu only.

Yeah bitcointalk is one place but i think reddit has more new people , people asking how to do setups and all. More active if i say so.

Also i belive monero community seems to be happy sponsoring professors and mesh networking prototypes and what not. A giving/sharing community so i think most folks would be positive about what you doing here.

As for xmrig developers might add somewere " to donate xmrig developers: xmr adress:   btc adress:  .

Well you get my point.
Yea, good point on the traffic and stuff.  When Vitalik called me on my cell phone back then I really didn't understand the gravity of the situation - at the time he sounded like he was designing a rocket engine, but it was so advanced... it's something I'll have to discuss some time.

So yes on the donate, I did put the 'suggestion' in the code, but yes good idea to make it on the display: I added it to the next version.

10-4 on the new users, that will be very good.

So an update for everyone, I did add the spork last night, and we can test that during the next release.  I believe I will be able to unit test that change locally so no rush.
I also erased my chain and resynced my local node, and I see it made it to the top block without a problem, so I believe this latest patch is all we needed for prod.

One side note guys that could help:  If anyone wants to try mining (solo mining in the wallet) against Prod in this random-x QT wallet (not randomx mining, regular POBH mining against prod).  Just make sure this 1.5.0.4 version syncs to the top in prod and solo mines (-erasechain=1 first).  This is for our regression testing (to ensure we didnt break any existing features before the RX cutover height).  We need to see that prod masternodes can also be seen in the Sanc list, and that the governance data is visible in this branch.

Finally, I am just about ready to create a wiki page for the game plan for 'corporate whitebranding'.  The reason this ties into testnet is we could potentially start the initiative (that replaces all of biblepay's branding information with monikers).  Monikers allow CSS, logos, brand slogans, narratives, and coin phrases to be replaced with the corporations identity.  I'm just mentioning this because if the plan becomes solid, we can potentially test part of this in testnet while we wait to upgrade to RX.  On a side note, I'm still shooting for a potential end of March roll-out.  (We can't upgrade more than once per quarter due to the exchange rules).  However I also don't want to release 'too much' good information at once for BiblePay as that might rocket us accidentally up to the top 5 coins too quickly, etc.




1755
TestNet Discussion Archive / Re: BIBLEPAY - RANDOMX INTEGRATION
« on: March 03, 2020, 09:36:12 AM »
Been testing on w10 latest release. Looks real solid. Later tonight gonna install on ubuntu 18.04 machines aswell.

Thanks, and I still have to release the latest nomp web site (with the extra parameter in the instructions)  and  look at the spork.

I wonder if we will be able to find some kind of monero forum we can post this in when we go live.  Like directly in the monero reddit.  It will be good to tiptoe in and try to be friends with monero, and not hostile.  As technically it would be best for all parties if we can help each other.  A hostile attitude would mean they would be inclined to change code to kick us out; but - if we can be friends - that would mean they help orphans and we remain stable for a long period.

I was definitely thinking bitcointalk dedicated page (like Togo suggested) for specific monero questions from new miners.

It feels to me like these new launch announcement threads dont have nearly the impact they used to.  I started one with BiblePay on cryptocointalk a while back and got like one reply, and
 it was basically someone asking me to go to work for them, etc.

But otoh, I think when we explain the dual revenue and First bitcoin branch to embrace RX, this could still be a different story.


Pages: 1 ... 110 111 112 113 114 115 116 [117] 118 119 120 121 122 123 124 ... 263