You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: pages/lessons/projects/1.mdx
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -297,7 +297,7 @@ contract WAGMI {
297
297
<Calloutemoji='💡'size='md'variant='info'>
298
298
While private and internal are not readable or modifiable from other contracts, its values are set on a public blockchain, making its values visible from the outside world.
299
299
</Callout>
300
-
300
+
301
301
#### Which visibility should I use ?
302
302
303
303
A simple answer to this is , start with giving every variable a `private` visibility then as you move further in contract developement modify variables to `internal` visibility as a next step of modification. Try to use `public` visibility as little as possible in order to be gas efficient and making less vulnerabilities in the smart contract.
@@ -705,7 +705,7 @@ you see the magical spell that is being cast here?
705
705

706
706
707
707
Before you go ahead and tell us: **what your future in web3 is,** have a check
708
-
on what you didn’t know a little while ago, and what you know now! \*
708
+
on what you didn’t know a little while ago, and what you know now! *
709
709
710
710
Apart from a user wallet, what else uses a blockchain (Ethereum) address?
711
711
@@ -726,4 +726,4 @@ Can a view function modify the state of the blockchain?
726
726
What can we use a smart contract for?
727
727
728
728
**Now, go to the community in Discord to share your new Open Sourcerer
0 commit comments