Jump to content

TaylorWarden

Member
  • Posts

    121
  • Joined

  • Last visited

Reputation Activity

  1. Haha
    TaylorWarden reacted to jargoman in Banking solutions for marijuana dispensaries   
    You just want to buy some pot with your XRP 
  2. Like
    TaylorWarden got a reaction from KarmaCoverage in Bitcoin on the XRP Ledger   
    Also:  https://en.wikipedia.org/wiki/Federation_(information_technology)
    Email addresses are an example of something that is federated.
  3. Like
    TaylorWarden got a reaction from KarmaCoverage in Bitcoin on the XRP Ledger   
    The RCL used to have a basic PHP implementation of the federation protocol where you as a gateway operator could add username@yourgatewaydomain.com to point towards a Ripple address.  Modified versions of this federation system allowed for the creation of the Bitcoin bridge.  The FinCEN fine in 2014 did not affect the federation implementations.
  4. Like
    TaylorWarden got a reaction from KarmaCoverage in Bitcoin on the XRP Ledger   
    The federation protocol they implemented was automated.  They were not pushing BTC transactions manually.
  5. Like
    TaylorWarden reacted to jargoman in The Aliens are here...   
    They've been on planet earth longer than mankind has existed there's no reason to sell precious XRP, let's not be rash.
  6. Like
    TaylorWarden got a reaction from KarmaCoverage in Bitcoin on the XRP Ledger   
    The Bridge worked by using federated addresses where the address was formed through your bitcoin receiver's address.  You would paste the receiving BTC address into the To field in your ripple client an add @snapswap.us for example.  SnapSwap would take the IOUs (or you could pay with XRP/another IOU if you were path-finding to their BTC IOUs) and deduct a small fee and the transaction fee.  Their bitcoin node would then send the remaining amount as a payment to the address specified.
  7. Like
    TaylorWarden got a reaction from KarmaCoverage in Bitcoin on the XRP Ledger   
    If anyone from spendthebits team ends up reading this thread, please consider implementing a Bitcoin bridge.
  8. Like
    TaylorWarden got a reaction from Triceratops in streetsofsilver.website - A Ripple Gateway serving Precious Metals, CAD, USD, BTC, and ETH IOUs   
    Here is my year in review for the performance of the Gateway. 
    We have KYC'd one person foreign to Canada and granted them membership to the SOS Gateway.  Shortly thereafter they registered they communicated that they were looking for an 'XRP Gateway.'  We did post sell orders of XRP in exchange for our CAD IOUs but no Canadians registered with the Gateway and we did not have any CAD Sell orders for other IOUs from other Gateways or XRP itself.  
    I was able to sell out our first position of silver before the price climbed above 30$CAD and we repurchased around the 28$ mark.  We were selling silver on the XRPL for spot plus physical premium of approximately 6-7.50$.  We did not make any sales of our XAG IOUs and I again sold the silver through private sales.  
    Due to the lack of interest in our services over this past year, the team has come to the decision to end the business operations effective immediately.  The corporation will still be retained by myself for future projects.  I do not believe I will be operating an XRPL Gateway again.  It has been a fun ~7 years of developing as a community Ripple developer and service provider.  I have gained many skills and insights into various fields of study (mostly software development & human psychology when it comes to interacting with cryptocurrencies) and I have found many colleagues along the way in my business ventures and my first forary into creating FOSS through the Quick Gateway Kit project.
    As of this moment, I am still available for consultation about creating and operating an XRPL Gateway.  Please feel free to get in contact with me through the appropriate channels.
    Cheers.
  9. Like
    TaylorWarden got a reaction from xrpholder in streetsofsilver.website - A Ripple Gateway serving Precious Metals, CAD, USD, BTC, and ETH IOUs   
    Here is my year in review for the performance of the Gateway. 
    We have KYC'd one person foreign to Canada and granted them membership to the SOS Gateway.  Shortly thereafter they registered they communicated that they were looking for an 'XRP Gateway.'  We did post sell orders of XRP in exchange for our CAD IOUs but no Canadians registered with the Gateway and we did not have any CAD Sell orders for other IOUs from other Gateways or XRP itself.  
    I was able to sell out our first position of silver before the price climbed above 30$CAD and we repurchased around the 28$ mark.  We were selling silver on the XRPL for spot plus physical premium of approximately 6-7.50$.  We did not make any sales of our XAG IOUs and I again sold the silver through private sales.  
    Due to the lack of interest in our services over this past year, the team has come to the decision to end the business operations effective immediately.  The corporation will still be retained by myself for future projects.  I do not believe I will be operating an XRPL Gateway again.  It has been a fun ~7 years of developing as a community Ripple developer and service provider.  I have gained many skills and insights into various fields of study (mostly software development & human psychology when it comes to interacting with cryptocurrencies) and I have found many colleagues along the way in my business ventures and my first forary into creating FOSS through the Quick Gateway Kit project.
    As of this moment, I am still available for consultation about creating and operating an XRPL Gateway.  Please feel free to get in contact with me through the appropriate channels.
    Cheers.
  10. Like
    TaylorWarden got a reaction from brianwalden in streetsofsilver.website - A Ripple Gateway serving Precious Metals, CAD, USD, BTC, and ETH IOUs   
    Here is my year in review for the performance of the Gateway. 
    We have KYC'd one person foreign to Canada and granted them membership to the SOS Gateway.  Shortly thereafter they registered they communicated that they were looking for an 'XRP Gateway.'  We did post sell orders of XRP in exchange for our CAD IOUs but no Canadians registered with the Gateway and we did not have any CAD Sell orders for other IOUs from other Gateways or XRP itself.  
    I was able to sell out our first position of silver before the price climbed above 30$CAD and we repurchased around the 28$ mark.  We were selling silver on the XRPL for spot plus physical premium of approximately 6-7.50$.  We did not make any sales of our XAG IOUs and I again sold the silver through private sales.  
    Due to the lack of interest in our services over this past year, the team has come to the decision to end the business operations effective immediately.  The corporation will still be retained by myself for future projects.  I do not believe I will be operating an XRPL Gateway again.  It has been a fun ~7 years of developing as a community Ripple developer and service provider.  I have gained many skills and insights into various fields of study (mostly software development & human psychology when it comes to interacting with cryptocurrencies) and I have found many colleagues along the way in my business ventures and my first forary into creating FOSS through the Quick Gateway Kit project.
    As of this moment, I am still available for consultation about creating and operating an XRPL Gateway.  Please feel free to get in contact with me through the appropriate channels.
    Cheers.
  11. Like
    TaylorWarden reacted to macropolo in Working Canadians to Death   
    Latest Ontario COVID outbreak caused by mistreatment of workers:
    https://macro.biz/working-canadians-to-death/
  12. Thanks
    TaylorWarden got a reaction from jbjnr in [FINTRAC] Large Virtual Currency Transaction Report Upload documentation   
    I am afraid that I believe that I am still obligated to file even if I am not the intermediary of performing the XRPL transaction.  I believe if the issuance of an IOU that is considered 10K or greater that is traded because the beneficiary of that amount of IOUs changes to a new account, I would be obligated to file.  If you trade >=10K with my market making account (which we do not have the means to fund to that level) then I would have to file.  I would also have to file for any deposit or withdrawal transaction a user commits to the Ripple Gateway.
    I do not have customers performing these high volume trades with me.  I will say that the greatest amount of funds deposited to a Gateway I have run in the past was 3000$ plus fee (to equal 3K IOUs issued) and the greatest withdrawal transaction I have performed to date would be approximately 3300$ and change.
  13. Thanks
    TaylorWarden got a reaction from RambeauTeasebox in Was I in the wrong for registering this domain name "with Ripple's brand trademarked name"?   
    Still awaiting a reply but due to the long weekend I probably won't receive any word back from support until at least tomorrow.  I wrote to Ripple Inc to ask if I can keep the domain registered and pointed at my github repo if I update the readme with multiple mentions that I am in no way affiliated with Ripple Inc.  If that is not good enough, then I have asked that they please purchase the domain name from me for only what I paid this year for the renewal fees, which is less than 60$USD.  I stated that I should be given just that much amount of respect since I have been a community developer and service provider for going on 6 years now (since the legal team would probably not be aware of this fact at all).
  14. Like
    TaylorWarden got a reaction from jbjnr in Was I in the wrong for registering this domain name "with Ripple's brand trademarked name"?   
    Still awaiting a reply but due to the long weekend I probably won't receive any word back from support until at least tomorrow.  I wrote to Ripple Inc to ask if I can keep the domain registered and pointed at my github repo if I update the readme with multiple mentions that I am in no way affiliated with Ripple Inc.  If that is not good enough, then I have asked that they please purchase the domain name from me for only what I paid this year for the renewal fees, which is less than 60$USD.  I stated that I should be given just that much amount of respect since I have been a community developer and service provider for going on 6 years now (since the legal team would probably not be aware of this fact at all).
  15. Haha
    TaylorWarden reacted to jargoman in Was I in the wrong for registering this domain name "with Ripple's brand trademarked name"?   
    Who could possibly be more charming than Brad Garlinghouse. His smile glints on queue. He brushes mega lawsuits off his impeccable suit. When he's not wooing television anchors or making competing c.e.o's soil themselves, he's arm in arm with christine lagaurde 

    We could go back to Larsen who hasn't smiled in 15 years. He likely has combat gear under his suit.  
  16. Thanks
    TaylorWarden got a reaction from RambeauTeasebox in Was I in the wrong for registering this domain name "with Ripple's brand trademarked name"?   
    Hi guys,
    Over a year ago now, I registered one of these new top level domain names to link to my Quick Gateway Kit repository on GitHub.  The name in question is ripplegateway.design.  I thought it would be interesting to put in my social media profiles to link back to my work.  At one point, I was thinking about creating a site where I would upload my latest CV and list prices for consultation and software development services, this never came to fruitition though.
    Today, I received this email from my domain registrar:
    My question is do you think that I was in the wrong for registering this domain name?  There are a few Ripple Gateways that were allowed to be "grandfathered" into allowing to operate a domain name with "Ripple" in it (name rippleisrael and ripplesingapore).  I'll have to unregister it and take the loss for the most recent renewal fee I paid for this domain name but oh well.  I just wonder why I am just now getting contacted about this when I've had this domain name for well over a year now?
    Does anyone think this is weird (the timing, I mean) or is it just Ripple trying to F with me a little bit because they claim is causes "confusion among our client's customers"?  Are their partners so dense that they cannot read that this is not an official Ripple repository?  This is frustrating me quite a bit.
  17. Thanks
    TaylorWarden got a reaction from RambeauTeasebox in Was I in the wrong for registering this domain name "with Ripple's brand trademarked name"?   
    Thanks for your comments on this situation everyone.  I wrote to support@ripple.com yesterday and recevied the typical automated response.  They probably won't get back to me in a while since it is Easter long weekend.  I am hoping that this will be able to come to a reasonable and fair conclusion.  I'm not too worried by it now but I was quite a bit frustrated yesterday.
  18. Like
    TaylorWarden reacted to RambeauTeasebox in Was I in the wrong for registering this domain name "with Ripple's brand trademarked name"?   
    @TaylorWarden I don't think you did anything "wrong," like in the moral/ethical sense. But you are using a U.S.-based domain name/website service provider (Namecheap) and Ripple has a trademark for the term "ripple" in the U.S., covering:
    So if you're using "ripple" for a case even somewhat related to the above, you've probably ran afoul of U.S. trademark law.
    Notice that the term "ripple" is trademarked by others and used for purposes unrelated to digital currency schemes. A card game, plant-based milk, handbags...
    Is Ripple being too zealous? Perhaps in your case, which seems pretty benign and in line with the grandfathered uses, but it's probably within their legal right. I don't know if a non-U.S. provider would respond differently or which other countries Ripple may have trademarks in, but it's something you could look into if you're set on using the name.
    https://tmsearch.uspto.gov/bin/gate.exe?f=doc&state=4809:kddgzu.4.9
    https://tmsearch.uspto.gov/bin/showfield?f=toc&state=4809%3Akddgzu.4.9&p_search=searchss&p_L=50&BackReference=&p_plural=yes&p_s_PARA1=&p_tagrepl~%3A=PARA1%24LD&expr=PARA1+AND+PARA2&p_s_PARA2=ripple&p_tagrepl~%3A=PARA2%24COMB&p_op_ALL=ADJ&a_default=search&a_search=Submit+Query&a_search=Submit+Query
    (I'm not a lawyer and this is not legal advice, just my personal opinion.)
  19. Like
    TaylorWarden reacted to at3n in Was I in the wrong for registering this domain name "with Ripple's brand trademarked name"?   
    @TaylorWarden if you're based in Canada, does Ripple's US trademark still affect you?
    I have no idea, but Ripple's email explicitly stated that it's registered in the US.
  20. Like
    TaylorWarden got a reaction from BillyOckham in Was I in the wrong for registering this domain name "with Ripple's brand trademarked name"?   
    Hi guys,
    Over a year ago now, I registered one of these new top level domain names to link to my Quick Gateway Kit repository on GitHub.  The name in question is ripplegateway.design.  I thought it would be interesting to put in my social media profiles to link back to my work.  At one point, I was thinking about creating a site where I would upload my latest CV and list prices for consultation and software development services, this never came to fruitition though.
    Today, I received this email from my domain registrar:
    My question is do you think that I was in the wrong for registering this domain name?  There are a few Ripple Gateways that were allowed to be "grandfathered" into allowing to operate a domain name with "Ripple" in it (name rippleisrael and ripplesingapore).  I'll have to unregister it and take the loss for the most recent renewal fee I paid for this domain name but oh well.  I just wonder why I am just now getting contacted about this when I've had this domain name for well over a year now?
    Does anyone think this is weird (the timing, I mean) or is it just Ripple trying to F with me a little bit because they claim is causes "confusion among our client's customers"?  Are their partners so dense that they cannot read that this is not an official Ripple repository?  This is frustrating me quite a bit.
  21. Like
    TaylorWarden got a reaction from SquaryBone in [FINTRAC] Large Virtual Currency Transaction Report Upload documentation   
    Well we got big news from FINTRAC today about LVCTR Reporting today.  Here is the info:
    There are five attachments to this email but the boards do not support those file types.  Therefore I've uploaded them to Google Drive to share.  Please be advised that these are first drafts and may change.
    https://docs.google.com/document/d/1NQJCPC-ye4HE66t6RBrj2IaQrKzUGhlptbVgTaqpHl0/edit?usp=sharing - DRAFT_Guidance_-_Reporting_large_virtual_currency_transactions_to_FINTRAC.PDF
    https://docs.google.com/document/d/1EmsMiQnuux4o1-eTKR9p2DqAKrIwlC4LGPnoantKLOY/edit?usp=sharing - DRAFT_Guidance_-_Reporting_large_virtual_currency_transactions_to_FINTRAC_FR.PDF
    https://drive.google.com/file/d/1fg-wGUZCitYn90K9yF6hBRQZ_5tiR6op/view?usp=sharing - LVCTR_Draft_Validation_Rules
    https://docs.google.com/document/d/16iB3xam-uNnhdP2eX96agKmy-OYNblcZ_PElk-rTLQg/edit?usp=sharing - JSON-LD schema for large virtual currency transaction reports (LVCTR)
    lvctr-2021.json:
    { $schema: "http://json-schema.org/draft-07/schema#", $id: "http://fintrac-canafe.gc.ca/reporting/api/lvctr/2021/schema#", title: "Large Virtual Currency Transaction Report Schema", type: "object", additionalProperties: false, properties: { $schema: { type: "string" }, @context: { type: "string", enum: [ "http://fintrac-canafe.gc.ca/reporting/api/lvctr/2021" ] }, @type: { type: "string", enum: [ "LvctrForm" ] }, reportingEntityNumber: { type: "number" }, reportReference: { $ref: "#/definitions/externalReportReference" }, definitions: { $ref: "#/definitions/ReportDefinition" }, details: { $ref: "#/definitions/LvctrFormDetails" }, transactions: { $ref: "#/definitions/LvctrTransaction" } }, required: [ "@context", "@type", "reportingEntityNumber", "reportReference", "details", "transactions" ], definitions: { ReportDefinition: { type: "array", items: { anyOf: [ { $ref: "#/definitions/LvctrPersonName" }, { $ref: "#/definitions/LvctrEntityName" }, { $ref: "#/definitions/LvctrPersonDetails" }, { $ref: "#/definitions/LvctrEntityDetails" } ] } }, LvctrTransaction: { type: "array", minItems: 1, maxItems: 99, items: { type: "object", additionalProperties: false, properties: { @type: { type: "string", enum: [ "LvctrTransaction" ] }, details: { $ref: "#/definitions/LvctrTransactionDetails" }, startingActions: { $ref: "#/definitions/LvctrStartingAction" }, completingActions: { $ref: "#/definitions/LvctrCompletingAction" } }, required: [ "@type", "details", "startingActions", "completingActions" ] } }, LvctrStartingAction: { type: "array", minItems: 1, maxItems: 50, items: { type: "object", additionalProperties: false, properties: { @type: { type: "string", enum: [ "LvctrStartingAction" ] }, details: { $ref: "#/definitions/LvctrStartingActionDetails" }, sourcesOfVirtualCurrency: { $ref: "#/definitions/LvctrSourceOfVirtualCurrency" }, conductors: { $ref: "#/definitions/LvctrConductor" } }, required: [ "@type", "details" ] } }, LvctrSourceOfVirtualCurrency: { type: "array", items: { type: "object", additionalProperties: false, properties: { @type: { type: "string", enum: [ "LvctrSourceOfVirtualCurrency" ] }, details: { $ref: "#/definitions/LvctrSourceOfVirtualCurrencyDetails" }, name: { $ref: "#/definitions/definition" } }, required: [ "@type", "details" ] } }, LvctrConductor: { type: "array", items: { type: "object", additionalProperties: false, properties: { @type: { type: "string", enum: [ "LvctrConductor" ] }, details: { $ref: "#/definitions/LvctrConductingDetails" }, subject: { $ref: "#/definitions/definition" }, onBehalfOfs: { $ref: "#/definitions/LvctrOnBehalfOf" } }, required: [ "@type", "details" ] } }, LvctrOnBehalfOf: { type: "array", items: { type: "object", additionalProperties: false, properties: { @type: { type: "string", enum: [ "LvctrOnBehalfOf" ] }, details: { $ref: "#/definitions/LvctrOnBehalfOfDetails" }, subject: { $ref: "#/definitions/definition" } }, required: [ "@type", "details" ] } }, LvctrCompletingAction: { type: "array", minItems: 1, maxItems: 50, items: { type: "object", additionalProperties: false, properties: { @type: { type: "string", enum: [ "LvctrCompletingAction" ] }, details: { $ref: "#/definitions/LvctrCompletingActionDetails" }, accountHolders: { $ref: "#/definitions/LvctrAccountHolder" }, involvements: { $ref: "#/definitions/LvctrInvolvement" }, beneficiaries: { $ref: "#/definitions/LvctrBeneficiary" } }, required: [ "@type", "details" ] } }, LvctrAccountHolder: { type: "array", items: { type: "object", additionalProperties: false, properties: { @type: { type: "string", enum: [ "LvctrAccountHolder" ] }, details: { $ref: "#/definitions/LvctrAccountHolderDetails" }, name: { $ref: "#/definitions/definition" } }, required: [ "@type", "details" ] } }, LvctrInvolvement: { type: "array", items: { type: "object", additionalProperties: false, properties: { @type: { type: "string", enum: [ "LvctrInvolvement" ] }, details: { $ref: "#/definitions/LvctrInvolvementDetails" }, name: { $ref: "#/definitions/definition" } }, required: [ "@type", "details" ] } }, LvctrBeneficiary: { type: "array", items: { type: "object", additionalProperties: false, properties: { @type: { type: "string", enum: [ "LvctrBeneficiary" ] }, details: { $ref: "#/definitions/LvctrBenefitingDetails" }, subject: { $ref: "#/definitions/definition" } }, required: [ "@type", "details" ] } }, LvctrFormDetails: { type: "object", additionalProperties: false, properties: { @type: { enum: [ "LvctrFormDetails" ] }, twentyFourHourAggregationTypeCode: { $ref: "#/definitions/optionTypeCode" }, twentyFourHourStartDateTime: { $ref: "#/definitions/zonedDateTime" }, twentyFourHourEndDateTime: { $ref: "#/definitions/zonedDateTime" }, ministerialDirectiveCode: { $ref: "#/definitions/string10" }, activitySectorCode: { $ref: "#/definitions/optionTypeCode" }, contactNumber: { $ref: "#/definitions/contactNumber" } }, required: [ "@type" ] }, LvctrTransactionDetails: { type: "object", additionalProperties: false, properties: { @type: { enum: [ "LvctrTransactionDetails" ] }, thresholdIndicator: { $ref: "#/definitions/boolean" }, transactionReference: { $ref: "#/definitions/string20" }, transactionDateTime: { $ref: "#/definitions/zonedDateTime" }, transactionMethodTypeCode: { $ref: "#/definitions/optionTypeCode" }, transactionMethodTypeOther: { $ref: "#/definitions/string200" }, transactionIdentifiers: { type: "array", items: { $ref: "#/definitions/string200" } }, transactionPurpose: { $ref: "#/definitions/string200" }, locationReference: { $ref: "#/definitions/locationReference" } }, required: [ "@type" ] }, LvctrStartingActionDetails: { type: "object", additionalProperties: false, properties: { @type: { enum: [ "LvctrStartingActionDetails" ] }, virtualCurrencyAmount: { $ref: "#/definitions/currencyAmount" }, virtualCurrencyTypeCode: { $ref: "#/definitions/string100" }, virtualCurrencyTypeOther: { $ref: "#/definitions/string200" }, canadianExchangeRate: { $ref: "#/definitions/string20" }, sendingVirtualCurrencyAddresses: { type: "array", items: { $ref: "#/definitions/string200" } }, obtained: { $ref: "#/definitions/string200" }, sourceOfVirtualCurrencyIndicator: { $ref: "#/definitions/boolean" }, conductorIndicator: { $ref: "#/definitions/boolean" } }, required: [ "@type" ] }, LvctrCompletingActionDetails: { type: "object", additionalProperties: false, properties: { @type: { enum: [ "LvctrCompletingActionDetails" ] }, dispositionTypeCode: { $ref: "#/definitions/optionTypeCode" }, dispositionTypeOther: { $ref: "#/definitions/string200" }, virtualCurrencyAmount: { $ref: "#/definitions/currencyAmount" }, virtualCurrencyTypeCode: { $ref: "#/definitions/string100" }, virtualCurrencyTypeOther: { $ref: "#/definitions/string200" }, receivingVirtualCurrencyAddresses: { type: "array", items: { $ref: "#/definitions/string200" } }, currencyTypeCode: { $ref: "#/definitions/alpha3" }, canadianEquivalentAmount: { $ref: "#/definitions/currencyAmount" }, referenceNumber: { $ref: "#/definitions/string200" }, otherRelatedNumber: { $ref: "#/definitions/string200" }, financialInstitutionNumber: { $ref: "#/definitions/string50" }, branchNumber: { $ref: "#/definitions/string50" }, accountNumber: { $ref: "#/definitions/string50" }, accountTypeCode: { $ref: "#/definitions/optionTypeCode" }, accountTypeOther: { $ref: "#/definitions/string200" }, accountCurrencyTypeCode: { $ref: "#/definitions/alpha3" }, accountVirtualCurrencyTypeCode: { $ref: "#/definitions/string100" }, accountVirtualCurrencyTypeOther: { $ref: "#/definitions/string200" }, accountOpenDate: { $ref: "#/definitions/localDate" }, involvementIndicator: { $ref: "#/definitions/boolean" }, beneficiaryIndicator: { $ref: "#/definitions/boolean" } }, required: [ "@type" ] }, LvctrSourceOfVirtualCurrencyDetails: { type: "object", additionalProperties: false, properties: { @type: { enum: [ "LvctrSourceOfVirtualCurrencyDetails" ] }, accountNumber: { $ref: "#/definitions/string50" }, policyNumber: { $ref: "#/definitions/string50" }, identifyingNumber: { $ref: "#/definitions/string50" } }, required: [ "@type" ] }, LvctrConductingDetails: { type: "object", additionalProperties: false, properties: { @type: { enum: [ "LvctrConductingDetails" ] }, clientIndicator: { $ref: "#/definitions/boolean" }, clientNumber: { $ref: "#/definitions/string50" }, username: { $ref: "#/definitions/string200" }, email: { $ref: "#/definitions/string200" }, deviceTypeCode: { $ref: "#/definitions/optionTypeCode" }, deviceTypeOther: { $ref: "#/definitions/string200" }, deviceIdentificationNumber: { $ref: "#/definitions/string200" }, deviceIpAddress: { $ref: "#/definitions/string200" }, requestDateTime: { $ref: "#/definitions/zonedDateTime" }, onBehalfOfIndicator: { $ref: "#/definitions/boolean" } }, required: [ "@type" ] }, LvctrBenefitingDetails: { type: "object", additionalProperties: false, properties: { @type: { enum: [ "LvctrBenefitingDetails" ] }, clientNumber: { $ref: "#/definitions/string50" }, username: { $ref: "#/definitions/string200" }, email: { $ref: "#/definitions/string200" } }, required: [ "@type" ] }, LvctrOnBehalfOfDetails: { type: "object", additionalProperties: false, properties: { @type: { enum: [ "LvctrOnBehalfOfDetails" ] }, clientNumber: { $ref: "#/definitions/string50" }, email: { $ref: "#/definitions/string200" }, relationshipTypeCode: { $ref: "#/definitions/optionTypeCode" }, relationshipTypeOther: { $ref: "#/definitions/string200" } }, required: [ "@type" ] }, LvctrAccountHolderDetails: { type: "object", additionalProperties: false, properties: { @type: { enum: [ "LvctrAccountHolderDetails" ] }, username: { $ref: "#/definitions/string200" } }, required: [ "@type" ] }, LvctrInvolvementDetails: { type: "object", additionalProperties: false, properties: { @type: { enum: [ "LvctrInvolvementDetails" ] }, accountNumber: { $ref: "#/definitions/string50" }, policyNumber: { $ref: "#/definitions/string50" }, identifyingNumber: { $ref: "#/definitions/string50" } }, required: [ "@type" ] }, LvctrPersonIdentificationDetails: { type: "object", additionalProperties: false, properties: { @type: { enum: [ "LvctrPersonIdentificationDetails" ] }, identificationTypeCode: { $ref: "#/definitions/optionTypeCode" }, identificationTypeOther: { $ref: "#/definitions/string200" }, identificationNumber: { $ref: "#/definitions/string50" }, identificationJurisdictionCountryCode: { $ref: "#/definitions/alpha2" }, identificationJurisdictionProvinceCode: { $ref: "#/definitions/alpha2" }, identificationJurisdictionProvinceOther: { $ref: "#/definitions/string100" } }, required: [ "@type" ] }, LvctrEntityIdentificationDetails: { type: "object", additionalProperties: false, properties: { @type: { enum: [ "LvctrEntityIdentificationDetails" ] }, identificationTypeCode: { $ref: "#/definitions/optionTypeCode" }, identificationTypeOther: { $ref: "#/definitions/string200" }, identificationNumber: { $ref: "#/definitions/string50" }, identificationJurisdictionCountryCode: { $ref: "#/definitions/alpha2" }, identificationJurisdictionProvinceCode: { $ref: "#/definitions/alpha2" }, identificationJurisdictionProvinceOther: { $ref: "#/definitions/string100" } }, required: [ "@type" ] }, LvctrStructuredAddress: { type: "object", additionalProperties: false, properties: { @type: { enum: [ "LvctrStructuredAddress" ] }, unitNumber: { $ref: "#/definitions/string10" }, buildingNumber: { $ref: "#/definitions/string10" }, streetAddress: { $ref: "#/definitions/string100" }, city: { $ref: "#/definitions/string100" }, district: { $ref: "#/definitions/string100" }, countryCode: { $ref: "#/definitions/alpha2" }, provinceCode: { $ref: "#/definitions/alpha2" }, provinceOther: { $ref: "#/definitions/string100" }, locality: { $ref: "#/definitions/string100" }, postalCode: { $ref: "#/definitions/string20" } }, required: [ "@type" ] }, LvctrUnstructuredAddress: { type: "object", additionalProperties: false, properties: { @type: { enum: [ "LvctrUnstructuredAddress" ] }, unstructuredCountryCode: { $ref: "#/definitions/alpha2" }, unstructuredAddressDetails: { $ref: "#/definitions/string500" } }, required: [ "@type" ] }, LvctrPersonDetails: { type: "object", additionalProperties: false, properties: { @type: { enum: [ "LvctrPersonDetails" ] }, $id: { $ref: "#/definitions/string32" }, givenName: { $ref: "#/definitions/string100" }, other: { $ref: "#/definitions/string100" }, surname: { $ref: "#/definitions/string100" }, alias: { $ref: "#/definitions/string100" }, address: { oneOf: [ { $ref: "#/definitions/LvctrStructuredAddress" }, { $ref: "#/definitions/LvctrUnstructuredAddress" } ] }, telephoneNumber: { $ref: "#/definitions/string20" }, telephoneExtension: { $ref: "#/definitions/string10" }, birthDate: { $ref: "#/definitions/localDate" }, residenceCountryCode: { $ref: "#/definitions/string200" }, occupation: { $ref: "#/definitions/string200" }, employerName: { $ref: "#/definitions/string100" }, identifications: { type: "array", items: { $ref: "#/definitions/LvctrPersonIdentificationDetails" } } }, required: [ "@type" ] }, LvctrEntityDetails: { type: "object", additionalProperties: false, properties: { @type: { enum: [ "LvctrEntityDetails" ] }, $id: { $ref: "#/definitions/string32" }, legalName: { $ref: "#/definitions/string100" }, address: { oneOf: [ { $ref: "#/definitions/LvctrStructuredAddress" }, { $ref: "#/definitions/LvctrUnstructuredAddress" } ] }, telephoneNumber: { $ref: "#/definitions/string20" }, telephoneExtension: { $ref: "#/definitions/string10" }, businessNature: { $ref: "#/definitions/string200" }, registrationIndicator: { $ref: "#/definitions/boolean" }, registrationNumber: { $ref: "#/definitions/string50" }, registrationJurisdictionCountryCode: { $ref: "#/definitions/alpha2" }, registrationJurisdictionProvinceCode: { $ref: "#/definitions/alpha2" }, registrationJurisdictionProvinceOther: { $ref: "#/definitions/string100" }, identifications: { type: "array", items: { $ref: "#/definitions/LvctrEntityIdentificationDetails" } }, authorizedPersons: { type: "array", items: { $ref: "#/definitions/LvctrPersonName" } } }, required: [ "@type" ] }, LvctrPersonName: { type: "object", additionalProperties: false, properties: { @type: { enum: [ "LvctrPersonName" ] }, $id: { $ref: "#/definitions/string32" }, givenName: { $ref: "#/definitions/string100" }, other: { $ref: "#/definitions/string100" }, surname: { $ref: "#/definitions/string100" } }, required: [ "@type" ] }, LvctrEntityName: { type: "object", additionalProperties: false, properties: { @type: { enum: [ "LvctrEntityName" ] }, $id: { $ref: "#/definitions/string32" }, legalName: { $ref: "#/definitions/string100" } }, required: [ "@type" ] }, definition: { type: "object", properties: { $ref: { type: "string", pattern: "^[a-z0-9]{1,32}$" } } }, externalReportReference: { type: "string", pattern: "[A-Z0-9_]+" }, contactNumber: { type: "number", minimum: 0 }, locationReference: { type: "string", pattern: "[A-Z0-9_]+" }, alpha2: { type: "string", minLength: 2, maxLength: 2 }, alpha3: { type: "string", minLength: 3, maxLength: 3 }, string10: { type: "string", minLength: 0, maxLength: 10 }, string20: { type: "string", minLength: 0, maxLength: 20 }, string32: { type: "string", minLength: 0, maxLength: 32 }, string50: { type: "string", minLength: 0, maxLength: 50 }, string100: { type: "string", minLength: 0, maxLength: 100 }, string200: { type: "string", minLength: 0, maxLength: 200 }, string500: { type: "string", minLength: 0, maxLength: 500 }, lookup: { type: "number", minimum: 0 }, integer: { type: "number", minimum: 0 }, optionTypeCode: { type: "integer", minimum: 1, maximum: 99999 }, currencyAmount: { type: "string", pattern: "^[0-9]*(\.[0-9]+)?$" }, zonedDateTime: { type: "string", pattern: "^[0-9]{4}-[0-9]{2}-[0-9]{2}T[0-9]{2}:[0-9]{2}:[0-9]{2}[\-\+][0-9]{2}:[0-9]{2}$" }, localDate: { type: "string", pattern: "^[0-9]{4}-[0-9]{2}-[0-9]{2}$" }, boolean: { type: "boolean" } } } Lots to discuss but I will be spending the weekend diving into these documents.  Once I have read them, I will return with my commentary.  In the meanwhile, please discuss.
  22. Like
  23. Like
    TaylorWarden reacted to tulo in XRP Ledger Technical community?   
    As far as I see it:
    -Building something on/for rippled (the core software): the codebase is very complex and Ripple's knowledge and technical skills and efficiency is way higher than anyone else out here. Moreover until recently most of the validators were controlled by Ripple, so any modification to ripple would still pass through them. Now it is possible with the recent decentralization, and maybe we'll see some amendments from the community in the future.
    -Building something on XRPL DEX (distributed exchange): one of the biggest problem is that the IOUs have counterparty risks. I've seen in 6 years a lot of gateways to disappear and I personally lost some non-negligible money because of this. Also Ripple never pushed a lot this feature. There are some indivuduals (or small groups) that built (private and a very few public) trading bot on it. I myself built some market making, arbitrage and frontrunning bots, but it's a hobby more than a large project.
    -Building something around XRP: the (powerful) API are there. I think ideas and entrepreneurs are missing.  Moreover I'm still personally skeptical about the technical capabilities of the network. Some ideal data were given, but a real test case was never published. Moreover technical papers destroyed some claims of the original white paper and we never gon an official answer.
  24. Haha
    TaylorWarden reacted to Sukrim in XRP Ledger Technical community?   
    Do you want to take part in discussions and do you have a project running or are you just interested in some "developer activity" metric for guessing how many USD your stack of XRP might be worth in 2 years from now?
  25. Like
    TaylorWarden got a reaction from SquaryBone in Publication of indicators of ML/TF related to virtual currencies   
    https://www.fintrac-canafe.gc.ca/guidance-directives/transaction-operation/indicators-indicateurs/vc_mltf-eng
    The above emphasis I provided in the list of indicators are the ones that I have deemed to be the most pertient indicators of ML/TF. 
    Please discuss.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.