Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion app/(docs)/dcs/pricing/legacy/page.md
Original file line number Diff line number Diff line change
Expand Up @@ -170,4 +170,4 @@ This helps cover the cost of payment processing and basic operations so we can c
- Any monthly usage that results in an invoice less than $5 will result in the minimum usage fee.
- If your usage exceeds $5 per month, you will not be charged a minimum usage fee.
- If you bought a starter package via a partner before August 1, 2025, you will not be charged a minimum usage fee until your starter package expires. The starter package expires one year from purchase or when the starter package credits have been fully used.
- If you pay with STORJ token, you will not be charged a minimum usage fee.
- If you pay with USDC, you will not be charged a minimum usage fee.
2 changes: 1 addition & 1 deletion app/(docs)/dcs/pricing/simplified/page.md
Original file line number Diff line number Diff line change
Expand Up @@ -109,7 +109,7 @@ Each tier has a few minimums that affect billing:
- **Minimum Monthly Usage:** A **$5 minimum monthly fee** applies to all active storage accounts. The minimum fee applies as follows:
- If your total usage for the month exceeds $5, no minimum fee is charged.
- If your total usage is less than $5, you are charged $5 for that month.
- Accounts paying with STORJ token are exempt from the minimum monthly fee.
- Accounts paying with USDC are exempt from the minimum monthly fee.
- Accounts on custom or negotiated contracts are not subject to the standard minimum fee. Your account team will communicate any applicable terms.
- The minimum fee does not apply during the free trial period. It takes effect at the start of your first billing cycle after the trial ends.
- Accounts with a $0 balance at the end of a billing cycle and no active storage will be suspended and then deleted. Free trial accounts are excluded from this.
Expand Down
2 changes: 1 addition & 1 deletion app/(docs)/dcs/pricing/tiered/page.md
Original file line number Diff line number Diff line change
Expand Up @@ -117,7 +117,7 @@ Each tier has a few minimums that affect billing:
- **Minimum Storage Duration (Active Archive tier only):** Data deleted before **30 days** will still be billed for the full 1 month period.
- **Minimum Monthly Usage:** A **$5 minimum monthly fee** applies to all active storage accounts. You won’t be charged the minimum if:
- Your usage exceeds $5
- You pay with **STORJ token**
- You pay with **USDC**
- You purchased a **starter package** prior to August 1, 2025 (valid until expiration).


Expand Down
8 changes: 4 additions & 4 deletions app/(docs)/learn/concepts/limits/page.md
Original file line number Diff line number Diff line change
Expand Up @@ -40,12 +40,12 @@ Adding a valid Payment method will result in your per-project limits being autom
Please note: some Debit cards maybe accepted too, but prepaid cards are not supported.
{% /callout %}

### STORJ token Payment method
### USDC Payment method

Adding $10 or more worth of STORJ tokens to your account deposit address will automatically upgrade your account to PRO and you will also receive a bonus of 10% of the deposit amount on your balance.
Adding $10 or more in USDC to your account deposit address will automatically upgrade your account to PRO. Deposits no longer receive a bonus.

{% callout type="info" %}
Please note: The deposit address currently only accepts transactions with ERC20 STORJ tokens on Ethereum mainnet or zkSync Era (note that **zkSync Lite is not supported**, and we are considering to sunset zkSync Era payments too).
Please note: The deposit address only accepts ERC20 USDC transactions on Ethereum mainnet. zkSync and other Layer 2 networks are not supported.
{% /callout %}

### Google Pay Payment method
Expand Down Expand Up @@ -76,4 +76,4 @@ We have also set the default limit for the number of segments to a healthy level

Customers can request a limit increase when needed by filling out the [limit increase request form](https://supportdcs.storj.io/hc/en-us/requests/new?ticket_form_id=360000683212) on our Storj support portal.

An automatic limit increase to Pro Account can be accomplished by adding a credit card or STORJ tokens (more or equal to $10) as a payment method. Please only make such requests if your use case requires more than the current default limits.
An automatic limit increase to Pro Account can be accomplished by adding a credit card or USDC (more or equal to $10) as a payment method. Please only make such requests if your use case requires more than the current default limits.
2 changes: 1 addition & 1 deletion app/(docs)/node/concepts/page.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ Before running your Storage Node for the first time, please note the Storage Nod
| | /tcp and /udp will allow your node to connect with the network via both TCP and UDP ports.
| | -p 28967:28967 is the core port used to connect with the network.
| | -p 14002:14002 is the port used for the storage node GUI dashboard. |
| `WALLET` | A wallet address to receive STORJ token payouts for running the node. |
| `WALLET` | A wallet address to receive USDC payouts for running the node. |
| `EMAIL` | Email address so we can notify you when a new version has been released. **(recommended)** |
| `ADDRESS` | External IP address or the DDNS you configured and the port you opened on your router \<ip>:\<port> If you are using a custom port other than 28967, you have to change the -p 28967:28967 to -p \<port>:28967 |
| `STORAGE` | How much disk space do you want to allocate to the Storj network? Be sure not to over-allocate space! Allow at least 10% extra for the overhead. If you over-allocate space, you may corrupt your database when the system attempts to store pieces when no more physical space is actually available on your drive. The minimum storage shared requirement is 500 GB, meaning you need a disk of at least 550 GB to allow for the 10% overhead. If you set up a new node, ensure the storage destination folder doesn't already have a config.yaml and/or storage folder inside, otherwise the storage node container could fail to start. |
Expand Down
2 changes: 1 addition & 1 deletion app/(docs)/node/faq/can-storj-use-other-blockchain/page.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,6 @@ Switching blockchains would either mean you end up on a less popular blockchain
Ethereum's roadmap actually contains many promising developments to address the scaling issues it has faced in the past, and zk-rollups are one of them. Some time ago, the best approach was to use a second-layer solution like zkSync Era, rather than risk using a less-proven blockchain.

Our project has already experienced blockchain migration in the past, when we migrated the Counterparty-based SJCX token (running on the Bitcoin blockchain) to the ERC-20 STORJ token on the Ethereum blockchain at a time when Bitcoin was experiencing scaling issues that made transactions with Counterparty tokens very expensive. While this migration initially mitigated the transaction fee problem, the Ethereum blockchain subsequently began to experience the same scaling issues and high fees. Therefore, we briefly used a second-layer solution such as Rollups (specifically zkSync Era) until Ethereum released version 2.0 to further address the scaling issues.
We have now [deprecated Layer 2](https://forum.storj.io/t/sunsetting-zksync-for-storagenode-payouts/32513) as Layer 1 fees have become acceptable.
We have now [deprecated Layer 2](https://forum.storj.io/t/sunsetting-zksync-for-storagenode-payouts/32513) as Layer 1 fees have become acceptable. Payouts to Storage Node Operators and customer deposits now use USDC on the Ethereum blockchain (Layer 1) instead of the STORJ token.

Thanks to René Smeekes (@BrightSilence) for summarizing all reasons in one [post](https://forum.storj.io/t/move-storj-to-the-xrpl-for-faster-payouts/13404/8?u=alexey).
Original file line number Diff line number Diff line change
@@ -1,18 +1,18 @@
---
title: Can we use an exchange as a wallet for STORJ tokens?
title: Can we use an exchange as a wallet for payouts?
docId: 857f3c8c-43ca-476a-9b2f-4883c415bcbf
redirects:
- /hc/en-us/articles/360060646292-Can-we-use-an-exchange-as-a-wallet-for-STORJ-tokens
- /hc/en-us/articles/360060646292
---
It is very important to note that an exchange address is not a valid address unless it is of the type that enables you to hold the private key yourself (decentralized exchange). See article [How do I hold STORJ? What is a valid address or compatible wallet?](docId:a045be02-e05a-11ef-9338-6045bd1fa4e3)
It is very important to note that an exchange address is not a valid address unless it is of the type that enables you to hold the private key yourself (decentralized exchange). See article [How do I hold USDC? What is a valid address or compatible wallet?](docId:a045be02-e05a-11ef-9338-6045bd1fa4e3)

In most cases, you do not control the private keys from the deposit address of the centralized exchanges, so all the funds in such an account are under the exclusive control of the exchange. This means that they can decide whether they will allow you to access any tokens you deposit there or not.

Since the deposit address is disposable, the exchange could also change it at any time without further notice, thus funds sent to an old deposit address after such a change could be lost.

Most of the exchanges use a separate deposit addresses for every token and if you send STORJ to the Ethereum deposit address for example, they could be lost. Exchanges post warnings about this on their deposit addresses so you may have no recourse if you ignore the warning and deposit STORJ to the wrong exchange deposit address anyway.
Most of the exchanges use a separate deposit addresses for every token and if you send USDC to a deposit address meant for a different token or network, it could be lost. Exchanges post warnings about this on their deposit addresses so you may have no recourse if you ignore the warning and deposit USDC to the wrong exchange deposit address anyway.

If you are a EU resident, you will be eligible to confirm the source address of funds due to MiCA changes, due to this mandatory requirement it's not possible for you to use the exchange address as your wallet address in the node's configuration at all, see the [relarted thread](https://forum.storj.io/t/getting-payed-to-kraken-address-with-mica/30295) on the forum.

We will not be able to assist to recover STORJ tokens if you have any problems with an exchange; in order to recover tokens, you will have to file a support ticket directly with the help desk of the exchange in question.
We will not be able to assist to recover USDC if you have any problems with an exchange; in order to recover tokens, you will have to file a support ticket directly with the help desk of the exchange in question.
2 changes: 1 addition & 1 deletion app/(docs)/node/faq/held-back-amount/page.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ redirects:

The **held back amount (staked)** component provides a preferred way for Node Operators to exit the network. This model optimizes liveliness by deterring Nodes to exit the network without transferring their pieces (thus limiting repair costs). Importantly, this strikes an equilibrium between a very low cost of entry for Nodes while also way to insulate against the cost of data repair.

Nodes don't need to provide any up-front stake to start earning STORJ tokens as a Storage Node Operator. Rather, during the first nine months of Storage Node Operation, a percentage of earnings are placed in a holding account. These funds are held until a Storage Node Operator chooses to leave the network. After the 15th month, a portion of the balance is returned to the Storage Node Operator, while the remainder is held indefinitely.
Nodes don't need to provide any up-front stake to start earning USDC as a Storage Node Operator. Rather, during the first nine months of Storage Node Operation, a percentage of earnings are placed in a holding account. These funds are held until a Storage Node Operator chooses to leave the network. After the 15th month, a portion of the balance is returned to the Storage Node Operator, while the remainder is held indefinitely.

If the Storage Node Operator uses the Graceful Exit function when leaving one or more satellites, the funds corresponding to the satellite(s) they exited will be returned in full after the exit is complete. If the Storage Node Operator exits the network abruptly without completing the Graceful Exit, the held back funds for all the satellites their node was operating on at the time of abrupt exit will be forfeited to offset the cost of data repair.

Expand Down
Loading
Loading