Twarden

Gateway
  • Content count

    306
  • Joined

  • Last visited

  • Days Won

    1

Twarden last won the day on February 19 2016

Twarden had the most liked content!

5 Followers

About Twarden

  • Rank
    Advanced Member

Contact Methods

  • Website URL
    https://xagate.com

Profile Information

  • Gender
    Male
  • Location
    Ontario, Canada
  • Occupation
    Ripple Gateway Operator
  • Country
  • Ripple Name
    ~Xagate and ~Rippleunion
  1. A bit of an update for the XAGATE Gateway. Ever since I was declined corporate prepaid credit cards from four different providers over this past year, I haven't given up on trying to find a solution for providing prepaid cards to clients, it has just been one of the greater barriers to entry for XAGATE to get off the ground with the vision statement of people being able to pay a merchant at a PoS with precious metals and/or crypto. I have continued my search into new deposit/withdrawal methods for Ripple users that are low cost and convenient. While I have been working on building an outbound bridge my initial plan was to use a combination of Wire Transfers and/or Western Union...but I found that the service fee to the end user would be exorbitant. I may have got lucky however as I found what seems to be a solid service provider which could perhaps be the basis for the CAD outbound bridge. I am currently waiting for my account to be KYC'd with this service so I can test it to see what features are working; I have already discovered a few caveats in so far but a couple of them have to do with who I bank with. As for new deposit methods a user suggested that I begin to accept Flexepin codes which can be purchased at most retailers such as Big Bee. I have an application in with them to become both a distributor and a merchant, so perhaps if their service is cost effective then users may be able to also redeem their IOUs for prepaid codes to use with other Flexepin merchants. As always, community feedback is a vital asset an is always greatly appreciated, so please post your questions, concerns, and suggestions or write to me via private message/email!
  2. http://www.fintrac-canafe.gc.ca/about-apropos/message-eng.asp
  3. I'm still interested about this project too @ripplerm Did you get my PM?
  4. Too bad Ripple doesn't care about the open source community any more..at least as much as it did a few years ago. One method to add 'paypal like functionalities' is to offer gift cards for XRP to hopefully entice users to not settle their position with an exchange or through a "traditional currency gateway." I hope for @lucky's sanity that he one day does not regret owning a 11,000$ jacket which just blows the Bitcoin pizza purchase on bct out of the water..
  5. It would be nice if the community eventually took to providing goods & services to further back the value of XRP.. If you look at the marketplace board on XRPchat, there are only three threads which are actually about buying/selling products for XRP: @lucky's leather jacket, a domain name (that infringes on Ripple Inc's copyright/branding guidelines), and a silver coin I was trying to sell a long time ago.
  6. For more information see here and here.
  7. @winthan Yes, I finally figured out why postgres got borked on ubuntu but no solution so far for my centos server. My ilp-kit is running on https://royalcrypto.com for CAD but I will switch this to BTC once I have a chance to install the yahoo connector plugin. By the way, don't you own https://ilp.milton.network?
  8. If you choose to configure the latter, I suggest looking at https://www.openswan.org/
  9. I am concerned about Gatehub/PBG issuing their gold as XAU on the RCL because they are not issuing XAU as XAU is the ISO currency code standard for 1 troy ounce (ozt) of .999 fine gold an meanwhile they are offering 1 XAU at a rate of 1g. When a user unknowingly trusts Gatehub's XAU and another Gateway's XAU then that user could potentially be ripped off for an great deal of value. I got a lot of flack on the official forums for wanting to issue fractional silver as XSG instead of issuing fractional amounts of XAG when I was discussing how I should set up my gateway's redemption policy which was settled on the latter as XAG would allow paths to be found easier. If Gatehub/PBG knew they were not dealing in troy ounces but grams then chose to ignore proper naming conventions and saw this as a non-issue then I think we have a problem; I propose we begin a critical discussion about Gateways and their usage of ISO standard currency issuances. I would like to ask @JoelKatz @nikb @mDuo13 to please comment on this issue if they can please find the time to do so either within this thread or over twitter.
  10. I am opening registration for all XAGATE clients to register their ripple accounts for a federated username@xagate.com address on the RCL. To register for an xagate.com account, please send an email to taylor@xagate.com with the subject "Federation Registration" and include: Your primary Ripple address (required) Your Full Name (required) Preferred username 1 (required) Preferred username 2 (required) Bitcoin Address (optional) Ethereum Address (optional) Your Ripple address and username@xagate.com will promptly be added to the federation protocol which works with the desktop wallet. No, this does not work in the Gatehub client. Perhaps @enej will implement federation support sometime this year "when the team isn't busy" but I wouldn't bother pestering them about this out of kindness (at least until maybe Q2 ;)). This is a free service and does not cost anything but your time to register. In other news, you can expect more XAG IOUs to hit the market on Monday, follow me on Twitter to get news when the trades are posted!
  11. Plesk runs nginx as a reverse proxy to Apache so both rules have to be set for the CORS header to be accepted.
  12. I was recently going insane with an .htaccess file plus all of my conf files because I was having issues with ripple.txt being discovered over HTTP. If you installed Plesk to your server then it creates a nginx reverse proxy that runs in front of Apache so you need to set two directives for the CORS header to be accepted, not just for Apache. Login to Plesk and from the Websites and Domains tab find your vhost, click Apache & nginx settings and add the following under Additional Apache Directives for HTTP and add the below block to Additional nginx directives: Go to https://ripple.com/build/ripple-txt-validator/ and enter your domain (without leading https or www) and it should report valid. Cheers.
  13. To have faith in the network, we would need to see all of the votes made. Here is the status of my validator's votes:
  14. Three or four is acceptable for fiat currencies to encourage market markers to set larger offers for a more competitive exchange rate. CAD.RippleUnion's ticksize will be set to 4 significant digits and the precious metals and cryptocurrency IOUs remitted by XAGATE will be set to 8 significant digits.
  15. Ticksize amendment is a feature for Gateways to choose which significant digits to round to for TakerPays and TakerGets to be calculated on offer preference. Gateway Operators can set this value from 3 to 15 significant digits. https://ripple.com/build/transactions/#offer-preference