mirror of
https://github.com/placeholder-soft/web.git
synced 2026-04-28 19:05:28 +08:00
docs: Add app blocklist info (#1155)
This commit is contained in:
@@ -1,45 +0,0 @@
|
||||
---
|
||||
title: Security
|
||||
slug: /security
|
||||
description: The Base bug bounty program and procedures for reporting vulnerabilities.
|
||||
keywords:
|
||||
[
|
||||
Base,
|
||||
bug bounty program,
|
||||
report vulnerability,
|
||||
bug report,
|
||||
cybersecurity,
|
||||
HackerOne,
|
||||
Base network,
|
||||
Bedrock,
|
||||
Optimism,
|
||||
vulnerability reporting,
|
||||
crypto security,
|
||||
open source,
|
||||
]
|
||||
hide_table_of_contents: true
|
||||
---
|
||||
|
||||
# Security
|
||||
|
||||
---
|
||||
|
||||
## Bug bounty program
|
||||
|
||||
In line with our strategy of being the safest way for users to access crypto:
|
||||
|
||||
- Coinbase will be extending our [best-in-industry](https://www.coinbase.com/blog/celebrating-10-years-of-our-bug-bounty-program) million-dollar [HackerOne bug bounty program](https://hackerone.com/coinbase?type=team) to cover the Base network, the Base bridge contracts, and Base infrastructure.
|
||||
- Coinbase will be working in tandem with OP Labs to harden the security guarantees of Bedrock and accelerate the timeline for decentralized fault-proofs on the [OP Stack](https://stack.optimism.io/).
|
||||
- Coinbase's bug bounty program will run alongside Optimism's existing [Immunefi Bedrock bounty program](https://immunefi.com/bounty/optimism/) to support the open source [Bedrock](https://stack.optimism.io/docs/releases/bedrock/) OP Stack framework.
|
||||
|
||||
---
|
||||
|
||||
## Reporting vulnerabilities
|
||||
|
||||
All potential vulnerability reports can be submitted via the [HackerOne](https://hackerone.com/coinbase) platform.
|
||||
|
||||
The HackerOne platform allows us to have a centralized and single reporting source for us to deliver optimized SLA's and results. All reports submitted to the platform are triaged around the clock by our team of Coinbase engineers with domain knowledge, assuring the best quality of review.
|
||||
|
||||
For more information on reporting vulnerabilities and our HackerOne bug bounty program, view our [security program policies](https://hackerone.com/coinbase?view_policy=true).
|
||||
|
||||
---
|
||||
51
apps/base-docs/docs/security/app-blocklist.md
Normal file
51
apps/base-docs/docs/security/app-blocklist.md
Normal file
@@ -0,0 +1,51 @@
|
||||
---
|
||||
title: How to avoid getting your app flagged as malicious
|
||||
slug: /security/app-blocklist
|
||||
description: The Base bug bounty program and procedures for reporting vulnerabilities.
|
||||
keywords:
|
||||
[
|
||||
Base,
|
||||
Coinbase Wallet,
|
||||
dapp,
|
||||
app,
|
||||
malicious warning,
|
||||
browser,
|
||||
dapp developer,
|
||||
app developer,
|
||||
best practice,
|
||||
unblock,
|
||||
remove warning,
|
||||
]
|
||||
hide_table_of_contents: true
|
||||
---
|
||||
|
||||
# How to avoid getting your app flagged as malicious
|
||||
|
||||
---
|
||||
|
||||
Ensuring that your app is perceived as trustworthy and not flagged as malicious requires attention to best practices. Here’s a quick guide on how to build a secure and compliant app from day one
|
||||
|
||||
## Smart Contracts
|
||||
|
||||
- **Verify Source Code:** Ensure that the source code of your contracts is verified and publicly available on [block explorers](https://docs.base.org/docs/tools/block-explorers/).
|
||||
- **Audit Your Contracts**: Having your contracts audited by a reputable firm is crucial. Publish the audit report and provide a reference link to it, so users can easily find it. Audits show that you’ve taken extra steps to secure your smart contracts.
|
||||
- **Limit User Funds Exposure**: Design your contracts to minimize the exposure of user funds. Use efficient design to reduce any unnecessary risk. For example, request the minimum amount needed to fulfill the transaction.
|
||||
|
||||
---
|
||||
|
||||
## App Best Practices
|
||||
|
||||
- **Accessibility Across Regions**: Avoid geo-blocking or access restrictions that prevent certain regions or countries from accessing your app.
|
||||
- **Consistent Web2 Behavior**: Avoid rapid or unexplained changes in UI that can make users feel uncertain about the app’s reliability.
|
||||
- **Transparent Web3 Interactions**: Make sure your app’s web3 interactions are clear and match the UI actions. For example, a “Mint” button should clearly emit a mint transaction.
|
||||
- **Standard Sign-in Methods**: Provide all standard connection methods for users to sign in, such as WalletConnect / WalletLink or popular browser extension wallets.
|
||||
|
||||
---
|
||||
|
||||
## Verification Request
|
||||
|
||||
Once you’ve implemented these best practices, consider submitting a verification request through the following [form](https://report.blockaid.io/). This step helps ensure that your app is recognized as safe and verified by trusted sources in the ecosystem.
|
||||
|
||||
By following these recommendations, you’ll significantly reduce the chances of your app being flagged as malicious and foster a secure and trustworthy environment for your users.
|
||||
|
||||
---
|
||||
18
apps/base-docs/docs/security/bounty.md
Normal file
18
apps/base-docs/docs/security/bounty.md
Normal file
@@ -0,0 +1,18 @@
|
||||
---
|
||||
title: Bug bounty
|
||||
slug: /security/bounty
|
||||
description: The Base bug bounty program
|
||||
keywords:
|
||||
[Base, HackerOne, bug bounty program, bug report, Base network, Bedrock, Optimism, open source]
|
||||
hide_table_of_contents: true
|
||||
---
|
||||
|
||||
# Bug bounty program
|
||||
|
||||
In line with our strategy of being the safest way for users to access crypto:
|
||||
|
||||
- Coinbase will be extending our [best-in-industry](https://www.coinbase.com/blog/celebrating-10-years-of-our-bug-bounty-program) million-dollar [HackerOne bug bounty program](https://hackerone.com/coinbase?type=team) to cover the Base network, the Base bridge contracts, and Base infrastructure.
|
||||
- Coinbase will be working in tandem with OP Labs to harden the security guarantees of Bedrock and accelerate the timeline for decentralized fault-proofs on the [OP Stack](https://stack.optimism.io/).
|
||||
- Coinbase's bug bounty program will run alongside Optimism's existing [Immunefi Bedrock bounty program](https://immunefi.com/bounty/optimism/) to support the open source [Bedrock](https://stack.optimism.io/docs/releases/bedrock/) OP Stack framework.
|
||||
|
||||
---
|
||||
29
apps/base-docs/docs/security/report.md
Normal file
29
apps/base-docs/docs/security/report.md
Normal file
@@ -0,0 +1,29 @@
|
||||
---
|
||||
title: Report vulnerability
|
||||
slug: /security/report
|
||||
description: The Base procedures for reporting vulnerabilities.
|
||||
keywords:
|
||||
[
|
||||
Base,
|
||||
report vulnerability,
|
||||
cybersecurity,
|
||||
HackerOne,
|
||||
Base network,
|
||||
Bedrock,
|
||||
Optimism,
|
||||
vulnerability reporting,
|
||||
crypto security,
|
||||
open source,
|
||||
]
|
||||
hide_table_of_contents: true
|
||||
---
|
||||
|
||||
# Reporting vulnerabilities
|
||||
|
||||
All potential vulnerability reports can be submitted via the [HackerOne](https://hackerone.com/coinbase) platform.
|
||||
|
||||
The HackerOne platform allows us to have a centralized and single reporting source for us to deliver optimized SLA's and results. All reports submitted to the platform are triaged around the clock by our team of Coinbase engineers with domain knowledge, assuring the best quality of review.
|
||||
|
||||
For more information on reporting vulnerabilities and our HackerOne bug bounty program, view our [security program policies](https://hackerone.com/coinbase?view_policy=true).
|
||||
|
||||
---
|
||||
@@ -86,7 +86,13 @@ module.exports = {
|
||||
items: ['tokens/token-list', 'tokens/wallet'],
|
||||
},
|
||||
['contracts'],
|
||||
['security'],
|
||||
{
|
||||
type: 'category',
|
||||
label: 'Security',
|
||||
collapsible: false,
|
||||
collapsed: false,
|
||||
items: ['security/bounty', 'security/report', 'security/app-blocklist'],
|
||||
},
|
||||
{
|
||||
type: 'link',
|
||||
label: 'Status',
|
||||
|
||||
Reference in New Issue
Block a user