> For the complete documentation index, see [llms.txt](https://docs.ramestta.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ramestta.com/welcome-to-ramestta/bridge/pos-vs-plasma-bridge.md).
# PoS vs Plasma Bridge
Moving between two large-scale blockchain networks requires a secure and robust cross-chain bridge, and Ramestta has achieved this by utilizing both Plasma and PoS(coming soon) security to create a trustless and bi-directional transaction environment between Ramestta and Polygon enables users to transfer tokens between the two networks without any third-party risks or impact on market liquidity. **The network bridge is designed to be fast, cost-effective, and flexible, and also serves as a scaling solution.** It utilizes a dual consensus architecture (Plasma + PoS platform) to prioritize speed and decentralization, and has deliberately enabled arbitrary state transitions on its sidechains along with EVM support.When your token crosses the bridge, it does not change its circulating supply:
* **Ramestta mints the same number of tokens** (1:1) as a pegged token **when a token leaves the Polygon network**.
* In order to move tokens back to the Polygon network, **they are burned on the Ramestta network and unlocked on the Polygon network** during the process.
#### PoS vs Plasma[](https://wiki.polygon.technology/docs/develop/ethereum-polygon/getting-started/#pos-vs-plasma)
| | PoS Bridge (Recommended) | Plasma Bridge |
| --------------------------------- | --------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------ |
| **Short description** | DApp Developers looking for flexibility and faster withdrawals with PoS system security | DApp Developers looking for increased security guarantees with Plasma exit mechanism |
| **Structure** | Highly flexible | Rigid, Less Flexible |
| **Deposit (Polygon →Ramestta)** | 22-30 mins | 22-30 mins |
| **Withdrawal (Ramestta→Polygon)** | 1 checkpoint = \~ 30 mins to 6 hours | Call to the process-exit procedure on Polygon's contract. |
| **Security** | Proof-of-Stake system, secured by a robust set of external validators | Ramestta’s Plasma contracts piggybacks on Polygon’s security |
| **Support Standards** | MATIC, RAMA20, RAMA721, RAMA1155 and others | Only MATIC, RAMA20, RAMA721 |
\
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.ramestta.com/welcome-to-ramestta/bridge/pos-vs-plasma-bridge.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.