Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reentrancy #57

Open
kristovatlas opened this issue Feb 2, 2024 · 0 comments
Open

Reentrancy #57

kristovatlas opened this issue Feb 2, 2024 · 0 comments
Assignees
Labels

Comments

@kristovatlas
Copy link

kristovatlas commented Feb 2, 2024

Reentrancy is a common source of vulnerabilities in other smart contract languages like Solidity.

Here's a Solidity example for reference: https://solidity-by-example.org/hacks/re-entrancy/

Common preventative measures in those languages are to audit code for use of the Checks-Effects-Interactions pattern, and use of libraries like OpenZeppelin's ReentrancyGuard. Code analysis tools like Slither also commonly test for reentrancy.

Given the utility in defi and other applications, it seems likely to me that Gnolang will one day support reentrancy in some form.

There's an open question as to whether reentrancy is currently achievable in Gnolang via MsgRun, which I plan to take a closer look at when time permits.

In the meantime, I wanted to create a thread on this topic and invite everyone to share their insights and ideas.

@kristovatlas kristovatlas self-assigned this Feb 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant