Kahroba/dev-procfile
8
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: record federation removal progress

Browse Source
This commit is contained in:
nfel
2026-08-30 19:16:25 +03:30
parent ae90ebed3a
commit 1bcab31ad7
2 changed files with 5 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
REFACTORING-AUDIT.md
+1
View File
@@ -404,3 +404,4 @@ Migration order implied by the map: isolate shared infrastructure constructors (
- Federation is not currently safe to delete outright: wallet persistence links `wallet.federation_id`, transaction records expose nullable `from_federation_id`/`to_federation_id`, generated wallet APIs expose federation messages, and wallet code still has federation lookup/creation paths.
- Auth has no active federation implementation; its wallet federation client is commented/dead code. Auth’s identity service should remain the owner of identity and national-ID data.
- The proposed target is reasonable only after consumers are migrated: `user_id → identity_id → wallet_id`, with `wallet_id` still scoped to `asset_id` and Stellar key derivation/custody explicitly preserved. W013 must first identify whether federation addresses or transaction routing are actually supported in production, then remove or retain the model based on evidence and a data/API compatibility plan.
- Per the requested migration, automatic federation creation is now removed from wallet initialization. New wallet creation uses user/asset identity and leaves federation assignment unset; Auth's dead federation client was deleted. Wallet federation tables, fields, generated API messages, and transaction routing fields still require the remaining W013 cleanup.