Skip to content

Edit T6 blog for clarity#542

Merged
max-digi merged 5 commits into
mainfrom
centaur/edit-t6-blog-clarity-1782253110
Jul 6, 2026
Merged

Edit T6 blog for clarity#542
max-digi merged 5 commits into
mainfrom
centaur/edit-t6-blog-clarity-1782253110

Conversation

@decofe

@decofe decofe commented Jun 23, 2026

Copy link
Copy Markdown
Member

Summary

  • Edited the T6 blog post for clarity, transitions, and readability while preserving its structure and plain technical voice.
  • Kept the original formatting, headings, lists, links, and technical meaning intact.
  • Confirmed the post does not use the supplied banned wording, contractions outside quotations, or the added AI-synonym avoid-list.

Prompted by: @0xalpharush

@vercel

vercel Bot commented Jun 23, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
tempo-docs Ready Ready Preview, Comment Jul 6, 2026 3:16pm

Request Review

Comment thread blogs/t6.md Outdated
Comment thread blogs/t6.md Outdated
Comment thread blogs/t6.md Outdated
Comment thread blogs/t6.md Outdated
Comment thread blogs/t6.md Outdated
Comment thread blogs/t6.md Outdated
Comment thread blogs/t6.md Outdated
Comment thread blogs/t6.md Outdated
Comment thread blogs/t6.md Outdated
Comment thread blogs/t6.md Outdated
Comment thread blogs/t6.md Outdated
@decofe decofe force-pushed the centaur/edit-t6-blog-clarity-1782253110 branch 7 times, most recently from 35d1b5f to f0a7dd9 Compare June 23, 2026 22:48
Comment thread blogs/t6.md Outdated
Comment thread blogs/t6.md Outdated
Comment thread blogs/t6.md Outdated
@decofe decofe force-pushed the centaur/edit-t6-blog-clarity-1782253110 branch from 425e2bd to 54d5e18 Compare June 23, 2026 23:05
@decofe decofe force-pushed the centaur/edit-t6-blog-clarity-1782253110 branch 3 times, most recently from b288e64 to c05a00f Compare June 23, 2026 23:10
Comment thread blogs/t6.md Outdated
Comment thread blogs/t6.md Outdated
@@ -9,35 +9,37 @@ category: network-upgrades

## Account-level receive policies

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be Receive Policies

Comment thread blogs/t6.md Outdated
## Account-level receive policies

Receive policies let an account specify which TIP-20 tokens it will accept and which addresses can send to it. This is useful for exchanges, custodians, on and off ramps, payment processors, and treasury systems that need to keep unsupported or unwanted assets out of balances, or limit who can send to an account.
Receive policies (TIP-1028) let an account specify which TIP-20 tokens it will accept and which addresses can send to it. This enables exchanges, custodians, on-and-off ramps, payment processors, and wallet platforms to avoid receiving unsupported or unwanted assets and/or to limit who can send to their accounts.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should remove the TIP name here since spec is linked at bottom of paragraph

Comment thread blogs/t6.md Outdated
- [TIP-1028: receive policies specification](https://tips.sh/1028)
- [TIP-1049: admin access keys specification](https://tips.sh/1049)
- [Receive policies specification](https://tips.sh/1028)
- [Admin access keys specification (TIP-1049)](https://tips.sh/1049)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should remove the TIP name here for consistency

Comment thread blogs/t6.md Outdated
*A blocked transfer still succeeds; the funds are held by the guard and stay recoverable by the configured party.*

Wallets, explorers, and indexers should treat held sends as their own state and listen for the `TransferBlocked` event, since blocked receipts are not enumerable onchain. For deposit flows that use TIP-1022 virtual addresses, the policy is resolved against the master account before the check runs, and receipts preserve the original recipient for attribution.
Wallets, explorers, and indexers should listen for the `TransferBlocked` event and index blocked transfers as blocked receipts are not enumerable onchain. For deposit flows that use virtual addresses (TIP-1022), the respective master account's policy is used, and receipts preserve the original recipient for attribution.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should remove the TIP name for consistency

@max-digi max-digi merged commit 4cc5cdc into main Jul 6, 2026
10 checks passed
@max-digi max-digi deleted the centaur/edit-t6-blog-clarity-1782253110 branch July 6, 2026 15:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants