fix broken links / asset path
tequ
5
.gitignore
vendored
@@ -22,3 +22,8 @@ pnpm-debug.log*
|
||||
|
||||
# jetbrains setting folder
|
||||
.idea/
|
||||
|
||||
# htmltest
|
||||
/bin/htmltest
|
||||
/tmp/.htmltest
|
||||
.htmltest.yml
|
||||
|
||||
|
Before Width: | Height: | Size: 49 KiB After Width: | Height: | Size: 49 KiB |
BIN
public/assets/hook-examples-senarios-1.png
Normal file
|
After Width: | Height: | Size: 46 KiB |
BIN
public/assets/hook-examples-senarios-2.png
Normal file
|
After Width: | Height: | Size: 40 KiB |
BIN
public/assets/hook-examples-senarios-3.png
Normal file
|
After Width: | Height: | Size: 42 KiB |
BIN
public/assets/hook-examples-senarios-4.png
Normal file
|
After Width: | Height: | Size: 98 KiB |
BIN
public/assets/hook-examples-senarios-5.png
Normal file
|
After Width: | Height: | Size: 98 KiB |
|
Before Width: | Height: | Size: 28 KiB After Width: | Height: | Size: 28 KiB |
|
Before Width: | Height: | Size: 91 KiB After Width: | Height: | Size: 91 KiB |
|
Before Width: | Height: | Size: 38 KiB After Width: | Height: | Size: 38 KiB |
|
Before Width: | Height: | Size: 26 KiB After Width: | Height: | Size: 26 KiB |
|
Before Width: | Height: | Size: 29 KiB After Width: | Height: | Size: 29 KiB |
|
Before Width: | Height: | Size: 36 KiB After Width: | Height: | Size: 36 KiB |
|
Before Width: | Height: | Size: 43 KiB After Width: | Height: | Size: 43 KiB |
|
Before Width: | Height: | Size: 210 KiB After Width: | Height: | Size: 210 KiB |
@@ -25,7 +25,7 @@ A Hook Chain is a sequence of up to **10** Hooks installed on an Xahau account.
|
||||
Hooks are installed into the chain using the [SetHook Transaction](/docs/hooks/concepts/sethook-transaction). When they are installed, the installer may specify install-time [Parameters](/docs/hooks/concepts/parameters) which may change the behaviour of the installed Hook.
|
||||
|
||||
<figure>
|
||||
|
||||
|
||||
<figcaption>*Example: Execution flow for a transaction passing through two Hook Chains*</figcaption>
|
||||
</figure>
|
||||
|
||||
|
||||
@@ -9,16 +9,16 @@ While working on Hooks we published a number of blogs on our progress, insights
|
||||
|
||||
#### 1. Receiving Hook executes additional logic
|
||||
|
||||
|
||||
|
||||
|
||||
#### 2. Receiving Hook blocks incoming transaction
|
||||
|
||||
|
||||
|
||||
|
||||
#### 3. Sending Hook blocks outgoing transaction
|
||||
|
||||
|
||||
|
||||
|
||||
#### 4. Hook controls an institutional account
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -15,7 +15,7 @@ Xahau is known and is being appreciated for its transaction throughput, speed an
|
||||
Hooks add smart contract functionality to Xahau: _layer one_ custom code to influence the behaviour and flow of transactions. Hooks are small, efficient pieces of code being defined on an Xahau account, allowing logic to be executed before and/or after Xahau transactions. These Hooks can be really simple, like: “reject payments < 10 XAH”, or “for all outgoing payments, send 10% to my savings account” or more advanced.
|
||||
|
||||
<figure>
|
||||
|
||||
|
||||
<figcaption>*Hooks high level concept*</figcaption>
|
||||
</figure>
|
||||
|
||||
|
||||
@@ -11,4 +11,4 @@ To avoid this burden (and high fees for end users) reference counting is used:
|
||||
* Subsequent installations by the same or other users for an identical Hook (i.e. with identical byte-code) increment the reference count. These installations point at the same object on the ledger. These transactions are billed in a similar way to setting a Trust Line, as the storage burden for the Hook was already paid for in the original Set Hook transaction.
|
||||
* While the reference count on the Hook Definition is greater than zero (meaning one or more accounts still have the Hook installed) the object remains on the ledger.
|
||||
|
||||
|
||||
|
||||
|
||||
@@ -56,7 +56,7 @@ This array _mirrors_ the [Hook Chain](/docs/hooks/concepts/chaining) installed o
|
||||
Each entry in the Hooks Array (in the SetHook Transaction) is called a _HookSet Object_, and its corresponding Hook in the account's Hook Chain is called the _Corresponding Hook_.
|
||||
|
||||
<figure>
|
||||
|
||||
|
||||
<figcaption>*Example: A user performs an operation on each Hook in his/her Hook chain with a SetHook transaction.*</figcaption>
|
||||
</figure>
|
||||
|
||||
@@ -67,7 +67,7 @@ Each Corresponding Hook is an object containing a _reference_ (pointer) to a `Ho
|
||||
The HookDefinition object is an unowned reference-counted ledger object that provides for de-duplication of identical web assembly bytecode. Two users using an identical hook will both point to the same HookDefinition.
|
||||
|
||||
<figure>
|
||||
|
||||
|
||||
<figcaption>*Example: Hook Definitions on Xahau*</figcaption>
|
||||
</figure>
|
||||
|
||||
|
||||
@@ -42,7 +42,7 @@ Hooks provide a versatile platform as they can be used for implementing a broad
|
||||
Hooks can be written in C or any other preferred language and then compiled into WebAssembly.
|
||||
|
||||
<figure>
|
||||
|
||||
|
||||
<figcaption>*Using Hooks Builder, you can develop, test, debug and deploy your own Hooks on our testnet, using our examples or building your own from scratch.*</figcaption>
|
||||
</figure>
|
||||
|
||||
|
||||
@@ -5,7 +5,7 @@ description: >-
|
||||
---
|
||||
When running a node, users will have to configure settings based on whether the node will run on the test network or the main network. When transitioning a single node from one network to the other, database files must be wiped, except wallet.db, which contains the server's identity credentials.
|
||||
|
||||
In addition to [building from scratch](/docs/infrastructure/building-xahau/index), there are three ways to install xahaud: Docker, locally, and using a portable binary. The below install methods all rely on the xahaud builds published at: [https://build.xahau.tech](https://build.xahau.tech), though the end result is different.
|
||||
In addition to [building from scratch](/docs/infrastructure/building-xahau), there are three ways to install xahaud: Docker, locally, and using a portable binary. The below install methods all rely on the xahaud builds published at: [https://build.xahau.tech](https://build.xahau.tech), though the end result is different.
|
||||
## Docker Container
|
||||
|
||||
To run xahaud in a Docker Container:
|
||||
|
||||
@@ -63,7 +63,7 @@ An `AccountRoot` object has the following fields:
|
||||
| `ImportSequence` | Number | UInt32 | No | The current sequence number from the importing account on the XAHL Ledger. |
|
||||
| `GovernanceFlags` | String | Hash256 | No | |
|
||||
| `GovernanceMarks` | String | Hash256 | No | |
|
||||
| `AccountIndex` | String | UInt64 | No | The account's \[Index Number]\[]. _(Added by the \[xahauGenesis amendment]\[] :enabled:)_ |
|
||||
| `AccountIndex` | String | UInt64 | No | The account's created index number. _(Added by the \[xahauGenesis amendment]\[] :enabled:)_ |
|
||||
| `TouchCount` | String | UInt64 | No | An incrementing counter for every time the ledger entry is "touched". |
|
||||
| `HookStateScale` | Number | UInt16 | No | Scale factor for determining when Hook state entries become stale. Valid values are `1` to `16` inclusive. _(Added by the [ExtendedHookState amendment][].)_ |
|
||||
|
||||
|
||||
@@ -1,7 +1,6 @@
|
||||
<!-- Currently, remarkPlugins does not support HMR, so you will need to restart the dev server if you change this file. -->
|
||||
[Internal Type]: /docs/protocol-reference/binary-format
|
||||
[Sequence Number]: /docs/protocol-reference/data-types/#account-sequence
|
||||
[Index Number]: /docs/protocol-reference/data-types/#index-number
|
||||
[SHA-512Half]: /docs/protocol-reference/data-types/#hashes
|
||||
[Specifying Time]: /docs/protocol-reference/data-types/#specifying-time
|
||||
[seconds since the Ripple Epoch]: /docs/protocol-reference/data-types/#specifying-time
|
||||
|
||||
@@ -13,11 +13,11 @@ EscrowFinish
|
||||
GenesisMint
|
||||
Import
|
||||
Invoke
|
||||
NFTokenAcceptOffer
|
||||
NFTokenBurn
|
||||
NFTokenCancelOffer
|
||||
NFTokenCreateOffer
|
||||
NFTokenMint
|
||||
// NFTokenAcceptOffer
|
||||
// NFTokenBurn
|
||||
// NFTokenCancelOffer
|
||||
// NFTokenCreateOffer
|
||||
// NFTokenMint
|
||||
OfferCancel
|
||||
OfferCreate
|
||||
Payment
|
||||
|
||||
@@ -58,7 +58,7 @@ We process your data under the following legal bases:
|
||||
|
||||
We use cookies to collect analytics and improve website performance. When you visit our site, a banner allows you to choose whether to accept or decline non-essential cookies.
|
||||
|
||||
For more information, please refer to our [Cookie Policy](#) (link to be added).
|
||||
For more information, please refer to our [Cookie Policy](/privacy-policy) (link to be added).
|
||||
|
||||
## 7. Data Sharing
|
||||
|
||||
|
||||
@@ -26,6 +26,7 @@ const parseRules: {
|
||||
const lines = content.split('\n')
|
||||
const result: { label: string; url: string }[] = []
|
||||
for (const line of lines) {
|
||||
if (line.startsWith('//')) continue
|
||||
if (line.length > 0) {
|
||||
const url = `/docs/protocol-reference/transactions/transaction-types/${line.toLowerCase()}`
|
||||
result.push({ label: `${line}`, url })
|
||||
|
||||