Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix broken links in read me #131

Open
wants to merge 6 commits into
base: develop
Choose a base branch
from
Open

Fix broken links in read me #131

Changes from 5 commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
ecfa9b1
added messages for custom token fee type and custom hbar fee type
anighanta Jun 14, 2021
477e874
fix broken links in readMe
anighanta Jan 4, 2022
1dd2755
merge main
anighanta Jan 4, 2022
9245070
fix typos
anighanta Jan 4, 2022
addd56a
merge develop
anighanta Jan 4, 2022
b3ed7b9
use ECDSA(secp256k1) to describe newly supported keys
anighanta Jan 10, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 9 additions & 9 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,31 +9,31 @@ from the _*.proto_ files in this repository:

There are five primary service families, which inter-operate on entities
controlled by one (or more) Ed25519 keypairs:
1. The [cryptocurrency service](services/CryptoService.proto),
1. The [cryptocurrency service](services/crypto_service.proto),
for cryptocurrency accounts with transfers denominated
in [hBar (ℏ)](https://help.hedera.com/hc/en-us/articles/360000674317-What-are-the-official-HBAR-cryptocurrency-denominations-).
2. The [consensus service](services/ConsensusService.proto), for
2. The [consensus service](services/consensus_service.proto), for
fast and unbiased ordering of opaque binary messages exchanged on
arbitrary topics.
3. The [smart contract service](services/SmartContractService.proto), for
3. The [smart contract service](services/smart_contract_service.proto), for
execution of Solidity contract creations and calls; contract may both possess
ℏ themselves and exchange it with non-contract accounts.
4. The [file service](services/FileService.proto), for storage and
4. The [file service](services/file_service.proto), for storage and
retrieval of opaque binary data.
5. The [token service](services/TokenService.proto), for token related operations such as create, update, mint, burn, transfer etc.
5. The [token service](services/token_service.proto), for token related operations such as create, update, mint, burn, transfer etc.

There are also three secondary service families:
1. The [network service](hedera/NetworkService.proto), for operations scoped
1. The [network service](services/network_service.proto), for operations scoped
to the network or its constituent nodes rather user-controlled entities as above.
2. The [scheduling service](services/ScheduleService.proto), for scheduling a transaction to
2. The [scheduling service](services/schedule_service.proto), for scheduling a transaction to
be executed when the ledger has received enough prequisite signatures.
3. The [freeze service](hedera/FreezeService.proto), for use by
3. The [freeze service](services/freeze_service.proto), for use by
privileged accounts to suspend network operations during a maintenance window.

It is important to note that most network services are gated by fees which
must be paid in ℏ from a cryptocurrency account. The payer authorizes a
fee by signing an appropriate transaction with a sufficient subset of the
Ed25519 key(s) associated to their account.
Ed25519/ECDSA_SECP256K1 key(s) associated to their account.

# Branching
This repository uses a simple branching model with only two distinguished branches:
Expand Down