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 1 commit
  5. 18 Jul, 2022 2 commits
  6. 11 Jul, 2022 1 commit
  7. 28 Jun, 2022 1 commit
  8. 27 Jun, 2022 1 commit
  9. 15 Jun, 2022 1 commit
  10. 02 May, 2022 2 commits
  11. 25 Apr, 2022 2 commits
  12. 11 Apr, 2022 1 commit
  13. 23 Mar, 2022 1 commit
  14. 14 Feb, 2022 2 commits
  15. 09 Feb, 2022 1 commit
  16. 17 Jan, 2022 1 commit
  17. 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
  18. 15 Dec, 2021 2 commits
  19. 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
  20. 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
  21. 01 Oct, 2021 1 commit
  22. 11 Aug, 2021 1 commit
  23. 02 Aug, 2021 1 commit
  24. 17 May, 2021 7 commits
  25. 08 Feb, 2021 1 commit
  26. 02 Feb, 2021 3 commits