AML/CFT compliance note and worked example script - #656
Open
AniekemeObot wants to merge 2 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a regulatory/compliance note on exchange-backed L2 rollups, using Ink as a case study (sequencer control, AML/CFT gaps, Travel Rule applicability, sanctions exposure, and cross-border jurisdiction questions).
Includes a worked example script (
scripts/get-latest-block.mjs) using ethers.js to query Ink's Sepolia testnet RPC and pull the latest block — supporting the traceability point made in the note.Intended as a general compliance/regulatory literacy resource for the Ink developer and builder community, not legal advice.