1. 26 Sep, 2022 1 commit
    • Filip Gospodinov's avatar
      core: improve sequence diagram numbering · 25e5ca57
      Filip Gospodinov authored
      For illustration purposes the sequence diagram depicting
      the advanced workflow also shows non-protocol actions.
      
      We remove the numbering from the illustrative actions to
      better distinguish them from the actual protocol.
      25e5ca57
  2. 29 Aug, 2022 2 commits
  3. 22 Aug, 2022 1 commit
    • Filip Gospodinov's avatar
      core: introduce requirement levels · ff2187bd
      Filip Gospodinov authored
      Human language is often ambiguous and it can be unclear
      to some that "can be obtained" implies optionality. The
      internet community has solved that problem in rfc2119.
      For TRP it makes sense to also adopt that standard which
      hopefully will resolve ambiguity in the specification.
      ff2187bd
  4. 25 Jul, 2022 2 commits
  5. 18 Jul, 2022 2 commits
  6. 11 Jul, 2022 1 commit
  7. 04 Jul, 2022 1 commit
  8. 28 Jun, 2022 1 commit
  9. 27 Jun, 2022 1 commit
  10. 15 Jun, 2022 1 commit
  11. 02 May, 2022 2 commits
  12. 25 Apr, 2022 2 commits
  13. 12 Apr, 2022 1 commit
  14. 11 Apr, 2022 1 commit
  15. 23 Mar, 2022 1 commit
  16. 21 Feb, 2022 1 commit
  17. 14 Feb, 2022 2 commits
  18. 09 Feb, 2022 1 commit
  19. 17 Jan, 2022 1 commit
  20. 20 Dec, 2021 1 commit
    • Dominik Spicher's avatar
      core: drop 'on-chain' references · c3b5cb5e
      Dominik Spicher authored
      Whereas not originally intended to do so, the references to
      "on-chain" transfers could be understood to restrict the scope of
      the TRP specification to base layer transactions, excluding such
      layer-two transfer mechanisms as the Lightning Network.
      
      This commit changes the relevant text locations to use a more
      inclusive "virtual asset transfer" or just plain "transfer".
      c3b5cb5e
  21. 15 Dec, 2021 2 commits
  22. 15 Nov, 2021 1 commit
    • Filip Gospodinov's avatar
      core: deprecate traditional work-flow · 37bd411d
      Filip Gospodinov authored
      The traditional workflow is deprecated because the use-case
      is contrived. If both, the originating and beneficiary VASP,
      use TRP then they will use lnurl. If one of them doesn't
      support TRP then the traditional workflow will also not be
      applicable.
      37bd411d
  23. 10 Nov, 2021 1 commit
    • Filip Gospodinov's avatar
      core: add Advanced workflow · 03b852ad
      Filip Gospodinov authored
      The Advanced workflow is designed to make the life
      easier for the compliance team. It solves the following issues:
      
      1. enables to decline transactions _a priori_ by using a transfer
         inquiry. This reduces the workload significantly for the
         compliance team.
      
      2. enables to negotiate a payment address _after_ the KYC checks
         have been completed. This eliminates _most_ unwanted payments.
      
      3. enables to share the transaction id _after_ the blockchain
         payment has been executed by using the transfer confirmation.
         This eliminates the need for signed but unbroadcasted transactions
         that require low-level tinkering and are risky because they
         can be executed by simply broadcasting them.
      03b852ad
  24. 04 Oct, 2021 1 commit
  25. 01 Oct, 2021 1 commit
  26. 11 Aug, 2021 1 commit
  27. 02 Aug, 2021 4 commits
  28. 21 Jul, 2021 1 commit
  29. 02 Jul, 2021 1 commit
  30. 17 Jun, 2021 1 commit
    • Harm's avatar
      Fix accountNumber, fix missing key, align example · 17affd13
      Harm authored and TravelRule Protocol's avatar TravelRule Protocol committed
      In the spec the 'originator' key has a map with two keys: originatorPersons and
      accountNumber. accountNumber was folded into originatorPersons and the later was
      misnamed originator. The top level key was missing altogether. Further more
      the example *did* show an array of originators but the OAS spec did not.
      17affd13