jcarbonnell/preTrainingNEAR huggingface dataset:
NEAR Web Wallet Security Update
COMMUNITY
August 4, 2022
The recent wallet hacks on other platforms have brought to light potentially serious security issues connected to the use of common analytics tools in Web3. In light of those hacks, we are sharing a perspective on a recent experience involving similar tools.

On June 6th, 2022, the NEAR Wallet team received a bug report indicating that sensitive information had been shared with a third party. The issue was fixed promptly the same day.

While the team was aware of this threat, and careful to sanitize data collected by the third party service, a code change nevertheless resulted in the collection of sensitive data for some users who had used email or SMS recovery with their wallets. Thankfully, @Hacxyk caught this before us and submitted the finding to our security team on June 6th (for which they have earned a bounty). The wallet team immediately remediated the situation, scrubbed all sensitive data, and identified any personnel who could have had the ability to access this data. 

To date, we have found no indicators of compromise related to the accidental collection of this data, nor do we have reason to believe this data persists anywhere.

Regardless, we no longer allow users to create accounts using email or SMS for account recovery. Despite having no evidence of compromise, we strongly recommend that users who have used email or SMS recovery options in the past rotate their keys. This can be accomplished by visiting wallet.nearpages.wpengine.com, either by enabling a Ledger device (your most secure option and highly recommended) or enabling passphrase security. After doing this, users should disable email or SMS recovery.

With the transition of the open source wallet codebase to the team at My NEAR Wallet, many improvements are in the works. 

We remind our users that the security of wallet accounts is of utmost importance to us–and it doesn’t stop with us either. User choices and behavior also impact security. Please consider using a hardware device, like a Ledger, to secure your wallet. Use only trusted and secured devices when creating and accessing your wallet. Never give out your recovery phrase or private keys.

You can learn more about the future of wallet.nearpages.wpengine.com here:

blog/near-opens-the-door-to-more-wallets/

The MyNearWallet team is also actively improving the security of wallets as outlined here:

https://medium.com/mynearwallet-blog/mynearwallet-security-statement-fd24265d91f2
```js
import { Wallet } from './near-wallet';

const DAO_FACTORY_CONTRACT_ADDRESS = "sputnik-dao.near";
const wallet = new Wallet({ createAccessKeyFor: DAO_FACTORY_CONTRACT_ADDRESS });
 
await wallet.viewMethod({
  method: 'get_dao_list',
  args: {},
  contractId: DAO_FACTORY_CONTRACT_ADDRESS
});
```

_The `Wallet` object comes from our [quickstart template](https://github.com/near-examples/hello-near-examples/blob/main/frontend/near-wallet.js)_
---
id: feature-request-and-bug-report
title: Feature Request and Bug Report
sidebar_label: Feature Request and Bug Report
description: NEAR Node Feature Request and Bug Report
---


<blockquote class="info">
<strong>Did You Know?</strong><br /><br />

As a node operator, you are welcome to create feature requests and submit bug reports on [Github](https://github.com/near/nearcore/issues) to improve the experience of running a node. Head to [`nearcore`](https://github.com/near/nearcore/issues) repository on Github to open an issue, and don't forget to tag the issue with the `nodeX` tag to indicate that this issue is related to `Node Experience`.

</blockquote>


## Feature Request and Bug Report {#feature-request-and-bug-report}

The NEAR team is actively solicitating feedback from the Node and Validator Community, and offers a process for the community to engage in feature / enhancement requests and to submit bug reports. Besides the existing NEAR Validator channels, the NEAR team is introducing a formal process for feature requests and bug reports.

With respect to the experience of operating a NEAR node, all bugs and feature enhancements are publicly tracked in the Github project tracker [`Node Experience`](https://github.com/orgs/near/projects/42). Node operators are welcome to create new issues for features and bugs, and to add these issues into the [Github project tracker](https://github.com/orgs/near/projects/42).

- **New Feature / Enhancement Request:**
  - Please create a [`Github issue`](https://github.com/near/nearcore/issues)
  - The issue will be reviewed and filtered through `Incoming Requests` column in the Github project [`Node Experience`](https://github.com/orgs/near/projects/42), where they will be groomed and slated for development based on priority

- **Bug Report:**
  - For node operator issues, please create a Zendesk issue here https://near-node.zendesk.com/hc/en-us/requests/new for the Node team, and try to attach your logs.


>Got a question?
<a href="https://stackoverflow.com/questions/tagged/nearprotocol">
  <h8>Ask it on StackOverflow!</h8></a>
NEAR Now Integrated into Ledger Live For More Security and Ownership
NEAR FOUNDATION
January 30, 2023
Wallet security can be intimidating, especially for newcomers. But it just got a whole lot easier for NEAR users. NEAR Foundation is excited to announce full integration with Ledger Live, making it easier than ever for NEAR holders to secure their assets using Ledger’s devices and software. 

Ledger Live is Ledger’s all-in-one digital asset management app enabling its users to manage and stake an ever-growing range of digital assets from the security and self-custody of their hardware wallets. Through its single, secure app, anyone from newcomers to crypto natives can follow the market,manage their DeFi portfolio, and explore Web3 with complete control and freedom. 

“We are thrilled to help more people enjoy the benefits of self-custody, no matter what their level of crypto experience,” said Marieke Flament, CEO of the NEAR Foundation. “This new partnership will bring even easier and more secure access to cryptocurrency worldwide, as we remain committed to serving as the de facto entry point to Web3 – simplifying the onboarding experience for users even if they have never used crypto, tokens, keys, or wallets.”

Carl Anderson, VP B2C Engineering at Ledger, adds: “I’m pleased to see a crypto player like NEAR join the Ledger ecosystem. This integration highlights what Ledger Live really is: an all-in-one asset management app where users can manage their digital assets, visualize their NFTs, and explore an ever-growing range of Web3 apps from the security of their hardware wallets.”

How Ledger Live works
To use Ledger Live, users must have a Ledger hardware wallet and then download the desktop and/or mobile app. This all-in-one digital asset management app allows users to track, buy, sell and swap an ever-growing range of tokens, visualize NFTs, earn rewards, manage NFT collections, and securely stake their digital assets with Ledger by Figment validator while enjoying the benefits of self-custody. 

Users can delegate their NEAR tokens to the Ledger by Figment validator, contributing to the protocol’s security while benefiting from coverage against slashing risks, low commission fees, and earning rewards from that contribution. 

Visit the Ledger Live webpage for more details on using the app and staking with the Ledger by Figment validator. 

DISCLOSURE NOTICE: Investment in cryptocurrency and other digital assets is highly speculative and comes with significant risks. The value of these assets can be highly volatile and may fluctuate significantly in a short period of time. It is important to conduct thorough research and consult with a financial advisor before making any investment decisions. Additionally, it is important to understand the regulatory environment and potential legal implications of investing in cryptocurrency. This disclosure is not a recommendation to buy or sell any particular asset and is for informational purposes only.
Case Study: NEAR Foundation’s Laura Cunningham on the NEAR Horizon Startup Accelerator
CASE STUDIES
July 26, 2023
NEAR is a home to a number of amazing apps and projects. These developers, founders, and entrepreneurs are using NEAR to effortlessly create and distribute innovative decentralized apps, while helping build a more open web — free from centralized platforms. In these Case Study videos, NEAR Foundation showcases some of these projects. 

In the latest NEAR Foundation Case Study video, viewers hear from Laura Cunningham, Team Lead at NEAR Horizon and General Manager at NEAR Foundation. NEAR Horizon is a Web3 accelerator program revolutionizing how founders and builders receive support in the open web. Laura takes viewers on a deep dive into Horizon’s startup accelerator marketplace, which the Horizon team built on the Blockchain Operating System (BOS). 

“The BOS was our platform of choice for building NEAR Horizon because it makes Horizon much more accessible to founders and projects that are already in the ecosystem. And then ones coming in new, you can be building on another chain as long as you have some component of your stack on NEAR then you can apply and be part of NEAR Horizon, ” she adds. “It is also incredibly composable, so we were able to fork different attributes that were already available on BOS and make use of them in our front end, so it made it a lot quicker to actually develop.”
---
id: explorer
title: Explorer
sidebar_label: Explorers
---
import Tabs from '@theme/Tabs';
import TabItem from '@theme/TabItem';

An Explorer allows you to quickly obtain information from the blockchain through a friendly user interface.
These useful tools enable for example to:

1. Search for a transactions and its receipts.
2. Check all the interactions in a smart contract.
3. See the balance of an account.
4. View block creations in real time

---

## NEAR Explorer

Created by NEAR, the [Near Explorer](https://nearblocks.io) enables to check information for transactions and accounts through a user-friendly interface.

![NEAR Explorer](/docs/assets/explorers/near-explorer.png)
*Main page of [NEAR Explorer](https://nearblocks.io)*

<hr className="subsection"/>

## Stats Gallery
Created by the community, [Stats Gallery](https://stats.gallery) gamifies the experience of looking to an account, adding levels and badges based on the account's activity. One of its
best features is that it allows you to see the contract's methods.

![Stats Gallery](/docs/assets/explorers/stats-gallery.png)
*Account view in [Stats Gallery](https://stats.gallery)*

<hr className="subsection"/>

## NearBlocks

Created by the community, [NearBlocks](https://nearblocks.io/) enables to check accounts and transactions with an interface similar to etherscan.

![NearBlocks](/docs/assets/explorers/nearblocks.png)
*Main page of [NearBlocks](https://nearblocks.io/)*

<hr className="subsection"/>

## Nearscope

[Nearscope](https://nearscope.net/) provides a NEAR node validator and delegator explorer.

![Nearscope](/docs/assets/explorers/nearscope.png)
*Main page of [Nearscope](https://nearscope.net/)*

<hr className="subsection"/>

## DappLooker

[DappLooker](https://dapplooker.com/) lets you analyze and query NEAR blockchain data, build dashboards to visualize data and share with your community.

![DappLooker](/docs/assets/explorers/dapplooker.png)
*Main page of [DappLooker](https://dapplooker.com/)*


<hr className="subsection"/>

## Pikespeak

[Pikespeak](https://pikespeak.ai/) provides access to real-time and historical data on the NEAR Protocol.
---
sidebar_position: 1
sidebar_label: "Introduction"
---

# Pagoda Alerts & Triggers

:::warning

Please be advised that these tools and services will be discontinued soon.

:::

## What are Alerts & Triggers?

Pagoda Alerts & Triggers are designed to notify, and automated responses to important events that occur on the NEAR blockchain. Behind the scenes, Alerts are powered by  many mini-indexers, “Alertexers”, that stream blockchain data in real-time, enabling developers to know what’s happening to their dApp before their users do.

Alerts are broken into three parts: 
1. The NEAR address the alert should listen to (account or contract)
2. The event condition (success & failed actions, account drains, and more)
3. The alert destination ([e-mail](setup.md#setting-up-e-mail-alerts), [Telegram](setup.md#setting-up-telegram-alerts), [webhooks](webhooks.md))

Alerts can be set-up to listen for the following five conditions: 
1. Successful Actions
2. Failed Actions
3. [Event Logged](https://nomicon.io/Standards/EventsFormat)
4. Function Called
5. Account Balance Change

## Setup

- [E-mail alerts](setup.md#setting-up-e-mail-alerts)
- [Telegram alerts](setup.md#setting-up-telegram-alerts)
- [Event Log Alerts](setup.md#setting-up-event-log-alerts)
- [Function Call Specific Alerts](setup.md#setting-up-function-call-specific-alerts)

## Using Webhooks with Alerts & Triggers

See an example on how to [set up alerts using webhooks](webhooks.md).
```bash
near call v2.keypom.near create_drop '{"public_keys": <PUBLIC_KEYS>, "deposit_per_use": "10000000000000000000000", "ftData": {"contractId": "ft.primitives.near","senderId": "bob.near", "amount": "1"}}}' --depositYocto 23000000000000000000000 --gas 100000000000000 --accountId bob.near
```
---
id: transactions
title: Transactions
---

Users interact with NEAR by creating transactions. Specifically, user's use their account's [private keys](./access-keys.md) to sign transactions, which are then broadcasted and processed by the network.

![](@site/static/docs/assets/welcome-pages/data-lake.png)

A transaction is composed of one or more [`Actions`](./transaction-anatomy.md), and each action costs a deterministic amount of [gas units](./gas.md). This gas units are translated into a cost in NEAR tokens, which the user must pay for the transaction to be processed.

:::tip
You can use an <a href="https://nearblocks.io/">Explorer</a> to inspect transactions in the NEAR network
:::
NEAR Wallet Will Remain Online Until the End of the Year
NEAR FOUNDATION
October 26, 2023
To avoid the rush of last minute transfers, and to support the inclusion of new wallets coming into the ecosystem, we are delaying the sunset of the NEAR wallet.

The NEAR wallet sunset is now targeted for December 31st, 2023.

We want to encourage users to continue to transfer their wallets using the Transfer Wizard available at wallet.near.org. Simply select “Get Started” on the banner at the top of the page displayed when you log in.

Learn more about how the Transfer Wizard works.
You can also learn more about why Pagoda is sunsetting the NEAR Wallet.
The future of the wallet.near.org landing page
Previously, we had intended to make wallet.near.org into a wallet-centric landing page as a place for ecosystem users to learn about all the amazing wallets available on the NEAR platform. However, due to resource and time constraints, we no longer believe we could provide the best experience. Instead, we are asking the community to create an information site that showcases all the NEAR wallets.

These plans are still in progress as we work with community partners. More to follow when we have more to share.

Thank you for your continued support and patience as we work hard to improve the user onboarding and transaction experience.
---
id: hardware
title: Hardware Requirements for Validator Node
sidebar_label: Hardware Requirements
sidebar_position: 1
description: NEAR Validator Node Hardware Requirements
---

This page covers the minimum and recommended hardware requirements for engaging with the NEAR platform as a validator node.


## Recommended Hardware Specifications {#recommended-hardware-specifications}

| Hardware       |  Recommended Specifications                                                  |
| -------------- | ---------------------------------------------------------------              |
| CPU            | x86_64 (Intel, AMD) processor with at least 8 physical cores                 |
| CPU Features   | CMPXCHG16B, POPCNT, SSE4.1, SSE4.2, AVX                                      |
| RAM            | 24GB DDR4                                                                    |
| Storage        | 2TB SSD (NVMe SSD is recommended. HDD will be enough for localnet only)      |

Verify CPU feature support by running the following command on Linux:

```
lscpu | grep -P '(?=.*avx )(?=.*sse4.2 )(?=.*cx16 )(?=.*popcnt )' > /dev/null \
  && echo "Supported" \
  || echo "Not supported"
```

## Minimal Hardware Specifications {#minimal-hardware-specifications}

| Hardware       |  Minimal Specifications                                                     |
| -------------- | ---------------------------------------------------------------             |
| CPU            | x86_64 (Intel, AMD) processor with at least 8 physical cores                |
| CPU Features   | CMPXCHG16B, POPCNT, SSE4.1, SSE4.2, AVX                                     |
| RAM            | 16GB DDR4                                                                    |
| Storage        | 1TB SSD (NVMe SSD is recommended. HDD will be enough for localnet only)   |

Verify CPU feature support by running the following command on Linux:

```
lscpu | grep -P '(?=.*avx )(?=.*sse4.2 )(?=.*cx16 )(?=.*popcnt )' > /dev/null \
  && echo "Supported" \
  || echo "Not supported"
```

## Cost Estimation {#cost-estimation}

Estimated monthly costs depending on operating system:

| Cloud Provider | Machine Size    | Linux                  |
| -------------- | --------------- | ---------------------- |
| AWS            | m5.2xlarge      | $330 CPU + $80 storage |
| GCP            | n2-standard-8   | $280 CPU + $80 storage |
| Azure          | Standard_F8s_v2 | $180 CPU + $40 storage |

<blockquote class="info">
<strong>Resources for Cost Estimation</strong><br /><br />

All prices reflect *reserved instances* which offer deep discounts on all platforms with a 1 year commitment

- AWS
  - cpu: https://aws.amazon.com/ec2/pricing/reserved-instances/pricing
  - storage: https://aws.amazon.com/ebs/pricing
- GCP
  - cpu: https://cloud.google.com/compute/vm-instance-pricing
  - storage: https://cloud.google.com/compute/disks-image-pricing
- Azure — https://azure.microsoft.com/en-us/pricing/calculator

</blockquote>

>Got a question?
<a href="https://stackoverflow.com/questions/tagged/nearprotocol">
  <h8>Ask it on StackOverflow!</h8></a>
John Smith joins NEAR Inc. as CISO to redefine safety in the Blockchain Ecosystem
NEAR FOUNDATION
October 29, 2021
We are thrilled to announce that John Smith has joined NEAR Inc as its Chief Information Security Officer (CISO). John will be leading NEAR Inc’s information security strategy, working closely with core development teams, partners, and the ever-expanding NEAR community.

“John has the right background, experience, and network to do the hard work of elevating trust in the blockchain community,” says Illia Polosukhin, the CEO of Near Inc.  “He comes to us with a history of solving complex technical problems at scale across challenging industries.”  

John is a seasoned cybersecurity professional—having led highly collaborative teams at iconic threat intelligence, security, and technology companies; serving clients at every scale across an array of industries.  In his previous role as the VP of Business Information and Product Security at the global ad ratings company Nielsen, he led all aspects of application and cloud security. At Nielsen, he transformed the relationship between developers and the security organization, shifting DevOps to DevSecOps. Early in his career, John also served at the US Nuclear Regulatory Committee, working on digital transformation, alongside reactor programs and human safety.  There he learned to understand and appreciate the detailed nuances of risk analysis, applied in complex high-stakes environments.

While John will be responsible for ensuring traditional security practices are maintained at NEAR, he will be particularly focused on developing and enabling scalable security practices for smart contract developers and ensuring the security of dApps when they go live.

Scalable Security 
Interest in DeFi continues to soar and NEAR is uniquely positioned to drive massive adoption of this revolutionary technology while continuing to build the foundations of Web3. 

NEAR Inc. is achieving this through dedication to developer friendliness, scalability, cross-chain interoperability, and performance. These are the features that drive adoption.

However, these features don’t guarantee that blockchain and cryptocurrency are free of issues. We’ve seen the ramifications of development mistakes and attacks on DeFi protocols and smart contracts.  

This creates another barrier to adoption—trust—and it limits the adoption of not just a single protocol, but all of Web 3.0. Ensuring the security of the NEAR protocol and elevating the practices of the entire NEAR development community are crucial to earning that trust and attracting new participants to take part in the future of finance and the web. 

We are excited that John has joined our team to help us achieve these goals. His work will help NEAR Inc. continue to build out a secure and scalable blockchain designed to onboard the world into Web3.
Case Study: Building on the NEAR Blockchain Operating System (BOS)
CASE STUDIES
July 24, 2023
NEAR is a home to a number of amazing apps and projects. These developers, founders, and entrepreneurs are using NEAR to effortlessly create and distribute innovative decentralized apps, while helping build a more open web — free from centralized platforms. In these Case Study videos, NEAR Foundation showcases some of these projects. 

In the latest NEAR Foundation Case Study video, viewers take a deep dive into the Blockchain Operating System (BOS). We explore how the BOS, like a decentralized app store, isn’t controlled by any centralized entities. Other topics of conversation include BOS Gateways, the discoverability and composability of BOS apps and components, building on the BOS with Javascript, and integrations with Visual Studio Code and Github.
---
id: sybil
title: Sybil Attacks
---

While developing your smart contract, keep in mind that an individual can potentially create multiple NEAR accounts. This is especially relevant in ecosystems involving crowd decisions, such as [DAOs](../../../2.build/5.primitives/dao.md). 

Imagine that you open the voting to anyone in the community. If each account can cast a vote, a malicious actor could span multiple accounts and gain a disproportionately large influence on the result.