Skip to content

Commit 0055efc

Browse files
committed
Further updates to white paper
1 parent 5fa3adf commit 0055efc

File tree

4 files changed

+7
-7
lines changed

4 files changed

+7
-7
lines changed

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
Transaction Authorization Improvement Proposals (TAIPs) provide standards for the [Transaction Authorization Protocol (TAP)](https://tap.rsvp).
44

5-
Please read the [TAP Whitepaper](https://hubs.ly/Q03BPp1k0) for more context.
5+
Please read the [TAP https://hubs.ly/Q03FRgly0](https://hubs.ly/Q03BPp1k0) for more context.
66

77
> [TAP](https://tap.rsvp) is a decentralized protocol allowing multiple participants in real-world transactions to identify each other and collaborate with the goal of authorizing them safely.
88

TAIPs/taip-1.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ description: Establishes the Transaction Authorization Protocol (TAP) framework
1111
## Transaction Authorization Protocol (TAP) Rationale
1212

1313
Currently there is not a good abstract and chain agnostic method for multiple parties to reason about and collaborate around blockchain transactions. As an example, in a typical blockchain transaction the only party able to authorize a transaction is the holder of a blockchain account. Smart contract based applications can implement authorization functionality within their code, but they do not work universally across different kinds of blockchains.
14-
As more and more businesses and individuals work to utilize blockchains for real world applications, it becomes increasingly important to be able to manage this. See the [TAP Whitepaper] for more.
14+
As more and more businesses and individuals work to utilize blockchains for real world applications, it becomes increasingly important to be able to manage this. See the [TAP https://hubs.ly/Q03FRgly0] for more.
1515

1616
## What is an TAIP?
1717

@@ -167,7 +167,7 @@ This document was derived heavily from [CAIP-1] written by Ligi, which was deriv
167167

168168
### References
169169

170-
[TAP Whitepaper]: https://hubs.ly/Q03BPp1k0
170+
[TAP https://hubs.ly/Q03FRgly0]: https://hubs.ly/Q03BPp1k0
171171
[CAIP-1]: https://chainagnostic.org/CAIPs/caip-1
172172
[markdown]: https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet
173173
[Bitcoin's BIP-0001]: https://github.com/bitcoin/bips

TAIPs/taip-4.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -489,7 +489,7 @@ The only potential PII that could be shared and leaked through this flow are pub
489489
## References
490490
<!--Links to external resources that help understanding the TAIP better. This can e.g. be links to existing implementations. See CONTRIBUTING.md#style-guide . -->
491491

492-
- [TAIP Whitepaper] The Transaction Authorization Whitepaper
492+
- [TAIP https://hubs.ly/Q03FRgly0] The Transaction Authorization https://hubs.ly/Q03FRgly0
493493
- [TAIP-2] Defines the TAP Message structure
494494
- [TAIP-3] Asset Transfer Message
495495
- [TAIP-5] Transaction Agents
@@ -510,7 +510,7 @@ The only potential PII that could be shared and leaked through this flow are pub
510510
[CAIP-10]: <https://chainagnostic.org/CAIPs/caip-10>
511511
[CAIP-19]: <https://chainagnostic.org/CAIPs/caip-19>
512512
[RFC 8905]: <https://datatracker.ietf.org/doc/rfc8905/>
513-
[TAIP Whitepaper]: <https://hubs.ly/Q03BPp1k0>
513+
[TAIP https://hubs.ly/Q03FRgly0]: <https://hubs.ly/Q03BPp1k0>
514514

515515
## Copyright
516516

_includes/blurb.html

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,8 +8,8 @@
88

99
<p></p>
1010
Please read the
11-
<a href="https://hubs.ly/Q03BPp1k0" title="TAP Whitepaper"
12-
>TAP Whitepaper</a
11+
<a href="https://hubs.ly/Q03BPp1k0" title="TAP https://hubs.ly/Q03FRgly0"
12+
>TAP https://hubs.ly/Q03FRgly0</a
1313
>
1414
for more context.
1515
</section>

0 commit comments

Comments
 (0)