diff --git a/Pledge pathrocknetwork b/Pledge pathrocknetwork
new file mode 100644
index 00000000..7e9b1acb
--- /dev/null
+++ b/Pledge pathrocknetwork	
@@ -0,0 +1,31 @@
+# Agoric Validator Pledge
+[pathrocknetwork](https://main.explorer.agoric.net/validator/agoricvaloper1uemhjcameshyrts58p38rkd7vmmfsry4z4xn3m)
+I, pathrocknetwork hereby commit to the following work and support for the benefit of the Agoric Network and Community. If, for any reason, I do not meet these commitments then I understand that I may lose delegation staked to me.:
+
+1. The hardware my node will run meets the requirements detailed in the [Agoric Validator Runbooks](https://github.com/Agoric/agoric-sdk/wiki/Runbook%...)
+
+2. My node will have an uptime of at least 95%
+
+3. I will set a reasonable commission rate between 3% to 10%
+
+4. I commit to not exceed 10% voting power
+
+5. I will actively participate in security and upgrade governance proposals found on [Commonwealth.im](https://commonwealth.im/agoric)
+
+6. I will report bugs I discover through the process described in the [Agoric Reporting a Security Bug Runbook](https://github.com/Agoric/agoric-sdk/wiki/Runbook%...)
+
+7. I will follow the guidelines described in the [Agoric Security Coordination - Emergency Bug Response with Chain Validators Runbook](https://github.com/Agoric/agoric-sdk/wiki/Runbook%...) to maintain the health of the chain
+
+8. I will notify impacted parties in case of node outage.
+
+9. I will strive to capture and share observability metrics to help diagnose and troubleshoot network and node performance issues
+
+10. I commit to network contributions listed below:
+
+Category 1: Infrastructure
+
+I will run an Agoric testnet node with an uptime of at least 95%, I will run an RPC endpoint , I will build a block explorer, validator dashboard, or other community tool
+[pathrocknetwork] (https://devnet.explorer.agoric.net/validator/agoricvaloper1jmauh4e06y4ksdxgmurl8avxvfnpr0xge4hvzp)
+Category 2: Community Growth
+
+I will contribute to the development of security best practices by creating and sharing technical documentation that includes writing incident response runbooks, configuration guides, or information for a validator wiki. ‌