[DOC] Test the new Go SDK Near library

[bucanero]

Documentation Type

New Documentation

What needs documentation?

Since there's a PR #2583 adding a new Go SDK to the Near toolbox, we need to test it out and confirm that Near devs can use it without issues.

• https://github.com/vlmoon99/near-sdk-go/
• https://github.com/vlmoon99/near-cli-go/

Acceptance Criteria

Following the Go quickstart guide should work Ok, so devs can build using this language.

Resources & References

No response

Priority

🟡 P2 : Documentation Enhancement

[matiasbenary]

Tested the Go CLI at https://github.com/vlmoon99/near-cli-go/.

Suggested adding early returns to prevent contract panics (e.g., lines 71, 78, 84).

Before

After

Tested the Go SDK at https://github.com/vlmoon99/near-sdk-go/.

• Typo fixes:

  • Function name GetAttachedDepoist() → GetAttachedDeposit()

  • Ideally: rename to attached_deposit to match Rust and JS SDK naming.

  • Log message: Attachet Deposit → Attached Deposit

• Recommend aligning with standard SDKs for:

  • Storage: storage_has_key(), storage_remove()

  • Crypto: sha256(), keccak256()

  • Promises: promise_create(), promise_then()

  • Validators: validator_stake(), validator_total_stake()

Reference links:

near-sdk-js/api.ts

near-sdk-rs/env.rs

[vlmoon99]

@matiasbenary
Thanks for your work - I’ve already fixed the issues with near-go-cli and near-sdk-go.
Regarding the naming conventions: I created the Near SDK specifically for Go developers, and in the Go ecosystem, different conventions are preferred compared to Rust or JavaScript developers. You can check the official Go style guide here: https://go.dev/doc/effective_go#mixed-caps

[vlmoon99]

I fixed near-go cli, all comment's u can see it inside pull request - #2583