Skip to content
36 changes: 35 additions & 1 deletion src/registry.json
Original file line number Diff line number Diff line change
Expand Up @@ -5490,6 +5490,40 @@
"checksum": "z4+3fdZhAyzb6R94sNJYeTuW/t7H48Qyuc3t72eraXw="
}
}
},
"npm:@kenostod/utl-snap": {
"id": "npm:@kenostod/utl-snap",
"metadata": {
"name": "UTL Protocol — Fee X-Ray & Passive Income",
"author": {
"name": "Kenostod Blockchain Academy LLC",
"website": "https://kenostodblockchain.com/utl-dashboard.html"
},
"summary": "Analyze MEV risk and UTL fee breakdown before signing any BNB Smart Chain transaction. View your KENO staking tier and protocol reward estimates inside MetaMask.",
"description": "The UTL MetaMask Snap adds Fee X-Ray analysis to BNB Smart Chain transactions — revealing MEV risk, UTL protocol fee breakdown, and distribution split before you sign. View your KENO staking tier (Bronze through Diamond) and accumulated reward estimates from UTL protocol fee flow. Flash Arbitrage Loan (FAL) alerts display real-time arbitrage data from the UTL protocol. Kenostod Blockchain Academy credentials are verifiable inside your MetaMask wallet. All features read on-chain state from 5 live UTL smart contracts on BNB Smart Chain — no funds are moved by the snap directly.",
"category": "transaction insights",
"tags": [
"defi",
"passive-income",
"staking",
"rewards",
"bsc",
"cross-chain",
"fee-redistribution",
"arbitrage",
"governance",
"education"
],
"support": {
"contact": "https://kenostodblockchain.com"
},
"sourceCode": "https://github.com/Keno2121/utl-metamask-snap"
},
"versions": {
"1.0.2": {
"checksum": "eiXsRHsgbgYNNzDZyOjWg1A3PZ5qX/1r5FjknJTYUNg="
}
Comment thread
cursor[bot] marked this conversation as resolved.
}
Comment thread
cursor[bot] marked this conversation as resolved.
Comment thread
cursor[bot] marked this conversation as resolved.
}
},
"blockedSnaps": [
Expand All @@ -5513,4 +5547,4 @@
"versionRange": "<=0.1.3"
}
]
}
}
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Trailing newline removed violating .editorconfig rule

Low Severity

The final } line of registry.json is replaced in a way that removes the trailing newline. The project's .editorconfig explicitly sets insert_final_newline = true for all files. This change violates that project-wide rule and will likely trigger CI linting failures or produce "No newline at end of file" warnings from git.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 746456d. Configure here.