- Notifications
You must be signed in to change notification settings - Fork6
License
sirduney/ord-with-dunes
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
ℹ️ This is a fork/based onapezord/ord-dogecoin
We included the real wonky block rewards from block 0 until block 144,999. We invite you to critically review our code insrc/epoch.rs
. We are convinced that doginals should use actual block rewards instead of a simplified version.
You should periodically create checkpoints of the redb database that you can restore from. Dogecoin has more reorgs than bitcoin due to its 1 minute block times and casey/ord does not handle reorgs. There is an open issuehere.
You can donate to apezord here:
BTC -1GKa8TBGK9UkY5PrigiP5eixDeYAsmdBC4
DOGE -DNmrp12LfsVwy2Q2B5bvpQ1HU7zCAczYob
ord
is an index, block explorer, and command-line wallet. It is experimentalsoftware with no warranty. SeeLICENSE for more details.
Ordinal theory imbues satoshis with numismatic value, allowing them tobe collected and traded as curios.
Ordinal numbers are serial numbers for satoshis, assigned in the order in whichthey are mined, and preserved across transactions.
Seethe docs for documentation and guides.
Seethe BIP for a technical description of the assignment andtransfer algorithm.
Seethe project board forcurrently prioritized issues.
Seemilestones to get a sense ofwhere the project is and where it's going.
Jointhe Discord server to chat with fellowordinal degenerates.
Tune in to theTwitch stream to watch us work on this project!
ord
relies on Dogecoin Core for private key management and transaction signing.This has a number of implications that you must understand in order to useord
wallet commands safely:
Dogecoin Core is not aware of inscriptions and does not perform satcontrol. Using
dogecoin-cli
commands and RPC calls withord
wallets maylead to loss of inscriptions.ord wallet
commands automatically load theord
wallet given by the--wallet
option, which defaults to 'ord'. Keep in mind that after runninganord wallet
command, anord
wallet may be loaded.Because
ord
has access to your Dogecoin Core wallets,ord
should not beused with wallets that contain a material amount of funds. Keep ordinal andcardinal wallets segregated.
Alphaord
wallets are not compatible with wallets created by previousversions oford
. To migrate, useord wallet send
from the old wallet tosend sats and inscriptions to addresses generated by the new wallet withord wallet receive
.
ord
is written in Rust and can be built fromsource. Pre-built binaries are available on thereleases page.
You can install the latest pre-built binary from the command line with:
curl --proto'=https' --tlsv1.2 -fsLS https://ordinals.com/install.sh| bash -s
Onceord
is installed, you should be able to runord --version
on thecommand line.
On Debian and Ubuntu,ord
requireslibssl-dev
when building from source:
sudo apt-get install libssl-dev
You'll also need Rust:
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
To buildord
from source:
git clone https://github.com/casey/ord.gitcd ordcargo build --release
The default location for theord
binary once built is./target/release/ord
.
ord
requiresrustc
version 1.67.0 or later. Runrustc --version
to ensure you have this version. Runrustup update
to get the latest stable release.
ord
requires a synceddogecoind
node with-txindex
to build the index ofsatoshi locations.ord
communicates withdogecoind
via RPC.
Ifdogecoind
is run locally by the same user, without additionalconfiguration,ord
should find it automatically by reading the.cookie
filefromdogecoind
's datadir, and connecting using the default RPC port.
Ifdogecoind
is not on mainnet, is not run by the same user, has a non-defaultdatadir, or a non-default port, you'll need to pass additional flags toord
.Seeord --help
for details.
ord
usesenv_logger. Set theRUST_LOG
environment variable in order to turn on logging. For example, runthe server and showinfo
-level log messages and above:
$ RUST_LOG=info cargo run server
Release commit messages use the following template:
Release x.y.z- Bump version: x.y.z → x.y.z- Update changelog- Update dependencies- Update database schema version