feat: add Telegram mini app connect for P2P access

web/public/docs/sdk/src/guides/async_backing_guide.rs

@@ -9,7 +9,7 @@
 //!
 //! > If starting a new teyrchain project, please use an async backing compatible template such as
 //! > the
-//! > [teyrchain template](https://github.com/pezkuwichain/pezkuwi-sdk/tree/master/templates/teyrchain).
+//! > [teyrchain template](https://github.com/pezkuwichain/pezkuwi-sdk/tree/main/templates/teyrchain).
 //! The rollout process for Async Backing has three phases. Phases 1 and 2 below put new
 //! infrastructure in place. Then we can simply turn on async backing in phase 3.
 //!

web/public/docs/sdk/src/guides/your_first_pallet/mod.rs

@@ -330,6 +330,7 @@
 //! [`pezpallet::pezpallet`]: pezframe_support::pezpallet
 //! [`pezpallet::config`]: pezframe_support::pezpallet_macros::config
 //! [`pezpallet::generate_deposit`]: pezframe_support::pezpallet_macros::generate_deposit
+//! [`frame`]: crate::pezkuwi_sdk::frame_runtime
 
 #[docify::export]
 #[pezframe::pezpallet(dev_mode)]

web/public/docs/sdk/src/guides/your_first_runtime.rs

@@ -169,6 +169,7 @@
 //!    [`crate::pezkuwi_sdk::templates`].
 //!
 //! [`SolochainDefaultConfig`]: struct@pezframe_system::pezpallet::config_preludes::SolochainDefaultConfig
+//! [`frame`]: crate::pezkuwi_sdk::frame_runtime
 
 #[cfg(test)]
 mod tests {

web/public/docs/sdk/src/pezkuwi_sdk/bizinikiwi.rs

@@ -133,6 +133,8 @@
 //!     - [`pezsc_consensus_beefy`] (TODO: @adrian, add some high level docs <https://github.com/pezkuwichain/pezkuwi-sdk/issues/305>)
 //!     - [`pezsc_consensus_manual_seal`]
 //!     - [`pezsc_consensus_pow`]
+//!
+//! [`frame`]: crate::pezkuwi_sdk::frame_runtime
 
 #[doc(hidden)]
 pub use crate::pezkuwi_sdk;

web/public/docs/sdk/src/reference_docs/frame_offchain_workers.rs

@@ -111,4 +111,6 @@
 //!
 //! - <https://forum.polkadot.network/t/offchain-workers-design-assumptions-vulnerabilities/2548>
 //! - <https://exchange.pezkuwichain.app/questions/11058/how-can-i-create-ocw-that-wont-activates-every-block-but-will-activates-only-w/11060#11060>
-//! - [Offchain worker example](https://github.com/pezkuwichain/pezkuwi-sdk/tree/master/bizinikiwi/pezframe/examples/offchain-worker)
+//! - [Offchain worker example](https://github.com/pezkuwichain/pezkuwi-sdk/tree/main/bizinikiwi/pezframe/examples/offchain-worker)
+//!
+//! [`frame`]: crate::pezkuwi_sdk::frame_runtime

web/public/docs/sdk/src/reference_docs/glossary.rs

@@ -54,7 +54,7 @@
 //! #### Dispatchable:
 //!
 //! Dispatchables are [function objects](https://en.wikipedia.org/wiki/Function_object) that act as
-//! the entry points in [FRAME](frame) pallets. They can be called by internal or external entities
+//! the entry points in [FRAME](crate::pezkuwi_sdk::frame_runtime) pallets. They can be called by internal or external entities
 //! to interact with the blockchain's state. They are a core aspect of the runtime logic, handling
 //! transactions and other state-changing operations.
 //!
@@ -68,7 +68,7 @@
 //!
 //! #### Pezpallet
 //!
-//! Similar to software modules in traditional programming, [FRAME](frame) pallets in Bizinikiwi are
+//! Similar to software modules in traditional programming, [FRAME](crate::pezkuwi_sdk::frame_runtime) pallets in Bizinikiwi are
 //! modular components that encapsulate distinct functionalities or business logic. Just as
 //! libraries or modules are used to build and extend the capabilities of a software application,
 //! pallets are the foundational building blocks for constructing a blockchain's runtime with frame.
@@ -118,3 +118,4 @@
 //! network.
 //!
 //! **Synonyms**: Teyrchain Validation Function
+//!

web/public/docs/sdk/src/reference_docs/mod.rs

@@ -93,10 +93,10 @@ pub mod cli;
 pub mod frame_runtime_upgrades_and_migrations;
 
 /// Learn about the offchain workers, how they function, and how to use them, as provided by the
-/// [`frame`] APIs.
+/// [`crate::pezkuwi_sdk::frame_runtime`] APIs.
 pub mod frame_offchain_workers;
 
-/// Learn about the different ways through which multiple [`frame`] pallets can be combined to work
+/// Learn about the different ways through which multiple [`crate::pezkuwi_sdk::frame_runtime`] pallets can be combined to work
 /// together.
 pub mod frame_pallet_coupling;
 

web/public/docs/sdk/src/reference_docs/runtime_vs_smart_contract.rs

@@ -19,7 +19,7 @@
 //!
 //! #### Smart Contracts in Bizinikiwi
 //! Smart Contracts are autonomous, programmable constructs deployed on the blockchain.
-//! In [FRAME](frame), Smart Contracts infrastructure is implemented by the
+//! In [FRAME](crate::pezkuwi_sdk::frame_runtime), Smart Contracts infrastructure is implemented by the
 //! [`pezpallet_contracts`] for WASM-based contracts or the
 //! [`pezpallet_evm`](https://github.com/polkadot-evm/frontier/tree/master/frame/evm) for EVM-compatible contracts. These pallets
 //! enable Smart Contract developers to build applications and systems on top of a Bizinikiwi-based
@@ -207,3 +207,4 @@
 //! - **For Smart Contract Developers**: Being mindful of the gas cost associated with contract
 //!   execution is crucial. Efficiently written contracts save costs and are less likely to hit gas
 //!   limits, ensuring smoother execution on the blockchain.
+//!

web/public/docs/sdk/src/reference_docs/trait_based_programming.rs

@@ -111,6 +111,8 @@
 //! - <https://github.com/pezkuwichain/pezkuwi-sdk/issues/326>
 //! - [Bizinikiwi Seminar - Traits and Generic Types](https://www.youtube.com/watch?v=6cp10jVWNl4)
 //! - <https://exchange.pezkuwichain.app/questions/2228/type-casting-to-trait-t-as-config>
+//!
+//! [`frame`]: crate::pezkuwi_sdk::frame_runtime
 #![allow(unused)]
 
 use pezframe::traits::Get;