Cohorts
  • Discover
  • About Us
  • Blog
  • Patika.dev
  • Web3

NEAR Developer Course

NEAR Certified Developer Final Project
What Does a Successful Project Look Like?
The Course Outline
NEAR CLI (Command Line Interface)
NEAR Explorer

What is Assembly Script?
Contract
File Structure
Imports
Practice I

Assert
Models
Context
Storage
Practice II

Collections
Arrays
Iteration
Classes

Introduction
Keys
Identity
Money

Smart Contract Overview
Account Model
View & Change Methods
Serde
NEAR Wallet
Practice: NEAR Academy-Meme Museum

Previous successful projects
Example: Thanks
Example: Guest Book
Example: Sample Lottery
Example: CRUD dApp
Develop project ideas
Submit and build your project plan

Loom video
Documentation and explanations
How to submit

View & Change Methods

There are only two methods in smart contracts, either you change the smart contract or view the smart contract.

Methods that do not update the state of your application are called view methods.

Those that do modify state are called change methods.

Calling a view method can be made without signing a transaction which means there is no account to charge for the work being done. But if we are not charging anyone and view methods are “free”, someone is surely paying (everything we do on a blockchain costs money because validators have to be compensated somehow). So who actually pays for executing a view call? Someone has to, right? Well, for now validators absorb the cost of executing view methods. This may change at some point in the future but for now you can execute methods that only read from the blockchain for free.

It’s worth noting that some operations are not allowed in view methods which can be confusing to new developers at first. The basic rule of thumb is “don’t do anything that requires a signature” (like trying to read Context.sender) because there is no signer (Context.sender is undefined) and “don’t do anything that can become too expensive” like making a cross-contract call (because this could potentially penalize validators).

We agreed that methods that do not update the state of your application are called view methods.

And those that do modify state are called change methods.

Please do NOT use create-near-app during this course as the code it generates will include frontend scaffolding which will almost certainly be too complicated for anything you’re trying to do at this point.

Quiz

Answer the questions to check your understanding.

This lesson includes a short quiz.

Previous
Next

Lesson discussion

Swap insights and ask questions about “NEAR Developer Course”.

Enroll to participate
Start the course to unlock the discussion. Enrolling helps us keep conversations relevant to learners.
Cohorts
WebsiteDiscoverBlogPatika.devRise In
CoursesCircleRustSoliditySolanaWeb3 FundamentalsBlockchain Basics
CompanyAbout UsTerms of UsePrivacy PolicyGDPR NoticeCookies
Don't miss any update!

Disclaimer: The information, programs, and events provided on https://cohorts.patika.dev is strictly for upskilling and networking purposes related to the technical infrastructure of blockchain platforms. We do not provide financial or investment advice, nor do we make any representations regarding the value, profitability, or future price of any blockchain or cryptocurrency. Users are encouraged to conduct their own research and consult with licensed financial professionals before engaging in any investment activities. https://cohorts.patika.dev disclaims any responsibility for financial decisions made by users based on the information provided here.

© 2026 Cohorts, All rights reserved