Skip to content

Glossary

Every term used in ARIADNE and in these pages, in alphabetical order. Each entry links to the page that explains it in full. Status names and labels are written as the web app shows them.

Accepted author. The submitter of an article, or a declared co-author who has confirmed by signing. Accepted authors share the article’s reputation and can never vote for, review or flag it. See Co-authors.

Address. The public identifier of an Algorand account, a string of 58 capital letters and digits. On ARIADNE your address is your identity: every action you sign is recorded under it. See Wallets and your address.

ALGO. The currency of Algorand. On ARIADNE it pays network fees and storage deposits; on TestNet it is free and has no value. See Costs and deposits.

Algorand. The public blockchain where ARIADNE’s record lives: a shared ledger that thousands of computers keep identical, where every action gets a date, an author and an order that nobody can change afterwards. See How it works in five minutes.

Amendment. A publication of type amendment that corrects an earlier article and points to it (its parent). It is a separate publication; the article it amends stays as it was. See New versions, amendments and retraction.

Application id. The number that identifies a deployed contract (an application) on an Algorand network. ARIADNE on TestNet is application 772983107. See Networks and addresses.

ARC standards. Algorand’s published conventions (Algorand Requests for Comments). ARIADNE uses ARC-71 for the non-transferable article token, ARC-19 to point that token at the article’s current version, ARC-28 for the events the contract emits, and ARC-56 to describe the contract to the programs that call it. See Contract methods and events.

Area. One of the six groups of fields in the OECD classification: Natural sciences, Engineering and technology, Medical and health sciences, Agricultural sciences, Social sciences, and Humanities. The app colours each field by its area. See Fields.

Article. A publication on ARIADNE: a folder on IPFS (index.md plus assets/) referenced by its CID from the blockchain, with its fields, type, status, versions, authors, reviews, comments and votes. “Article” is also the name of the main type. See Articles and their statuses.

Article number. The number the contract gives each publication, in order, starting at 1 on each application. It appears in links such as /testnet/a/12. See Articles and their statuses.

Article token. A non-transferable token (an ARC-71 ASA, unit name ARIA) that the contract creates with each publication to prove authorship in any wallet. Claiming it is optional; once claimed it is frozen in your account, and 0.1 ALGO stays there as long as you hold it. See What is on the blockchain, and what is not.

ASA. Algorand Standard Asset, Algorand’s built-in kind of token. ARIADNE’s article token is one. See What is on the blockchain, and what is not.

Assets folder. The optional assets/ folder of an article, holding figures, data and any file the text refers to by a relative path such as assets/fig-1.svg. See Write the article.

Bibliography. A reference list made from any list of articles, sorted and formatted in one of eight citation formats, ready to copy or save as a file. See Lists and bibliographies.

Box. A named piece of storage that the contract keeps on the blockchain for one record (an article, a review, a vote…). The action that creates a box pays its storage deposit. See What is on the blockchain, and what is not.

CAR file. A content archive: one file that carries an IPFS folder with all its blocks. The Upload tab builds one in your browser and sends it to your pinning service. See Storage: IPFS, pins and copies.

Changes requested. The seal state shown when at least two reviews that count ask for major revision or rejection, and they are as many as the favourable ones or more. See The Peer-reviewed seal.

CID. Content identifier: the fingerprint of a file or folder on IPFS, computed from its content, so that any change gives a different CID. The blockchain stores each version’s CID. Article CIDs start with bafy, review and comment CIDs with bafk. See Storage: IPFS, pins and copies.

Citation. An ARIADNE article cites another when it links to its page, writes its DOI or the CID of one of its versions, or amends it; the header’s references count too. Retracted citing articles are not counted. See Citations and Thread Score.

Claim. The transaction by which an author adds to their reputation the share of an article’s votes they are entitled to. Votes for an article accumulate on the article; each author claims their own share, within the daily limit. See Claim your reputation.

Closed version. The status an author gives an article, from under review, to stop new versions (“final” on the blockchain). It says nothing about review; the seal does. See Articles and their statuses.

Co-author. An address declared in an article when it is published (at most 25; the list never changes). A co-author confirms by signing from their own wallet and then shares the article’s reputation equally with the other authors. See Co-authors.

Comment. A public message on an article, with nested replies, mentions and mathematics. Comments are allowed in every status; they earn a little reputation from votes, and 5 when the submitter resolves them. See Comment, mention and vote.

Conflict of interest. For the seal, a review does not count when its author has the same verified ORCID iD as an author of the article, wrote an ARIADNE article with one of them or has works with one of them on OpenAlex within 3 years of the review, or has the same current institution on the public ORCID records. See The Peer-reviewed seal.

Daily limit. An address can gain at most 50 reputation per field per day (a UTC day), from all sources together. Article reputation beyond it stays claimable on later days; for reviews and comments the excess is lost. See Reputation and vote weight.

DataCite. A registry of DOIs. On MainNet, DOIs from repositories other than Zenodo are checked with DataCite. See Get a DOI with Zenodo.

Deposit. The ALGO an action pays for the storage it creates on the blockchain (technically, the increase in the minimum balance requirement, or MBR, of the contract’s account). Deposits are not paid to anyone and are not refunded: they stay locked as long as the record exists, which is forever. See Costs and deposits.

Dispenser. The Algorand service that gives free TestNet ALGO, at https://bank.testnet.algorand.network. See Wallets and your address.

Dispute, disputed. An article becomes disputed automatically when the flags of the current round add up to 30. Votes and reputation claims pause, reviews and comments continue, and governance resolves the dispute: cleared (the article returns to its earlier status) or retracted. See Flags, disputes and governance.

DOI. Digital Object Identifier, the persistent identifier of scholarly publishing. An ARIADNE article can get one through Zenodo; an author declares it on the blockchain and the indexer checks it. See Get a DOI with Zenodo.

Ed25519. The ordinary signature scheme of Algorand accounts. The web app’s cost previews assume an Ed25519 wallet. See Wallets and your address.

Explorer. A website that shows Algorand transactions and accounts. The app links each confirmed transaction to the Lora explorer. See Networks and addresses.

Falcon. Falcon-1024, the post-quantum signature scheme that Algorand supports since version 5.0. ARIADNE’s governance account uses it; a Falcon-signed transaction pays 0.003 ALGO instead of 0.001. See Wallets and your address.

Field. A subject from the OECD Fields of Science classification (42 fields in 6 areas), identified by a number such as 0x0303 (Health sciences). Each article has a primary field and optionally a secondary one, both fixed at publication; reputation is kept per field. See Fields.

Filebase. A pinning service that the Upload tab can use with your own IPFS RPC API token. See Your first article, step by step.

Flag. A signal that an article is plagiarised, spam, fabricated or otherwise unacceptable, from someone with at least 10 reputation in its primary field. Flags weigh like votes but are not votes; enough of them make the article disputed. See Flag an article.

Follow. A public, permanent record that you follow an address: its publications, reviews and comments then appear in your inbox on every device. Unfollowing marks the follow inactive. See Follow people and get notified.

Front-matter. The header at the top of index.md, between two --- lines: title, authors, fields, type, parent, abstract and more. The keys that the blockchain also records must match it. See The article header (front-matter).

Gateway. A web server that serves IPFS content over HTTPS. ARIADNE’s gateway, https://ipfs.ariadne.press, serves only content that ARIADNE’s node already holds. See Storage: IPFS, pins and copies.

Genesis hash. The identity of an Algorand network. Every transaction carries it, so a transaction prepared for TestNet is rejected on MainNet. See TestNet and MainNet.

Governance. A single account with two powers only: registering new fields and resolving disputes (it can also hand its role to a new address). It cannot edit, hide or delete anything or change the rules, and it is a post-quantum (Falcon) account. See Flags, disputes and governance.

In peer review. The seal state of an article that has reviews that count, but not yet two favourable ones that outnumber the unfavourable. See The Peer-reviewed seal.

Inbox. Your notifications (replies, mentions, reviews and comments on your articles, co-author invitations, new followers) and the activity of the people you follow. See Follow people and get notified.

index.md. The required file of an article folder: the text in Markdown, starting with the front-matter. See Write the article.

Indexer. The service that reads every ARIADNE transaction and builds the feed, profiles, inbox, search, citations and the seal. It also checks articles, ORCID iDs and DOIs, and keeps a second copy of the content. Anyone can run one and get the same results. See Run an indexer.

IPFS. The InterPlanetary File System, a network where a file is found by a fingerprint of its content (its CID) instead of its location. ARIADNE stores articles, reviews and comments there. See Storage: IPFS, pins and copies.

Kubo. The reference implementation of IPFS. ARIADNE’s server runs a Kubo node for the second copy and the gateway; authors can run one to pin their own folders. See Host the full stack.

List. A named collection of articles. Private lists stay in your browser; public lists are recorded on the blockchain and appear on your profile. See Lists and bibliographies.

LocalNet. A private Algorand network on a developer’s computer, used to develop and test ARIADNE. It is never offered on ariadne.press. See Host the full stack.

MainNet. Algorand’s main network, where ALGO have real value. ARIADNE opens there after an independent audit of the contract. See TestNet and MainNet.

MBR. Minimum balance requirement. See Deposit and Minimum balance.

Mention. A reference to a person in a comment, written @name.algo or @ADDRESS. Up to 5 people per comment are recorded on the blockchain and notified. See Comment, mention and vote.

Minimum balance. The ALGO an Algorand account must keep and cannot spend: 0.1 ALGO for every account, plus 0.1 while it holds a claimed article token. See Wallets and your address.

Network fee. What Algorand charges per transaction, currently 0.001 ALGO (a publication is three transactions). Unlike a deposit, it is spent. See Costs and deposits.

NFD. Non-Fungible Domains, a naming service on Algorand. Where an address has a verified name ending in .algo, ARIADNE shows the name instead of the address; the name is a convenience, not a certificate of identity. See Identity: addresses, names and ORCID.

OpenAlex. An open index of scholarly works. For a verified ORCID iD, ARIADNE reads from it the person’s citation counts for the profile, and the works used by the seal’s expertise and conflict-of-interest rules. See The Peer-reviewed seal.

ORCID iD. The persistent identifier of a researcher, from orcid.org. You can link yours to your address; once your public ORCID record lists your ARIADNE profile, readers see your name. It never changes your reputation. See Link your ORCID iD.

Path A, Path B. The two ways to publish from the web app. Path A, the Upload tab, builds and pins the folder in your browser; Path B, I have a CID, takes a folder you pinned yourself. See Publish an article.

Peer-reviewed. See Seal.

Pin. To keep a file online on IPFS. The author is responsible for at least one pin; ARIADNE’s indexer pins a second copy, and anyone can add more. See Storage: IPFS, pins and copies.

Pinata. A pinning service that the Upload tab can use with your own key (a JWT); its CAR uploads need a paid plan. See Your first article, step by step.

Pinning key. The key of your Filebase or Pinata account that the website uses to pin your articles, reviews and comments. It stays in your browser only, is sent only to that service, and Forget it removes it. See Your first article, step by step.

Post-quantum account. See Falcon.

Preprint. The status of an article when it is published: its first public version. New versions are allowed. See Articles and their statuses.

Primary field. The main field of an article, chosen at publication. Votes, reviews and flags on the article weigh by reputation in this field, and the article’s reputation goes to it. See Reputation and vote weight.

Recommendation. The verdict of a review: accept, minor revision, major revision or reject. Accept and minor revision are favourable for the seal. See Review an article.

Recovery phrase. The secret words your wallet showed you when you created your account. They give full control of your address: never share them. See Wallets and your address.

Reputation. A whole number per address and per field, earned only from what others do: votes for your articles, reviews marked useful, votes for your comments, resolved comments. It never decreases, and it sets the weight of your votes in that field. See Reputation and vote weight.

Resolve. The submitter of an article can mark a comment by someone who is not an author as resolved, once; the commenter gains 5 reputation. See Comment, mention and vote.

Retracted. The last status of an article, withdrawn by its author or by governance after a dispute. It stays readable and permanently marked; it takes no more votes, reviews or claims. See New versions, amendments and retraction.

Review. A signed, permanent assessment of an article: a recommendation and a written report, at most one per person per article, never by its own authors. Others can mark it useful, which earns the reviewer reputation. See Review an article.

Seal. The Peer-reviewed seal: an article holds it while at least two reviews that count are favourable and outnumber the unfavourable ones. The indexer computes it; later reviews can take it away, and it is suspended while the article is disputed. See The Peer-reviewed seal.

Secondary field. An optional second field of an article, chosen at publication. It receives half of the reputation an author claims in the primary field. See Reputation and vote weight.

Smart contract. A program that lives on the blockchain and runs exactly as written. ARIADNE’s contract holds the record and enforces its rules; it cannot be modified or deleted. See Contract methods and events.

Submitter. The address that published an article, its first author. Only the submitter can publish new versions, change the status and resolve comments. See Publish an article.

TestNet. Algorand’s public test network, where ALGO are free. ARIADNE runs there today; articles and reputation on TestNet carry no value on MainNet. See TestNet and MainNet.

Thread Score. ARIADNE’s citation measure, from 0 to 100 (50 is typical). An article’s score places it among the articles of its field by the citations it received from other people, compared at the same age; a person’s score is the weighted mean of their articles’ scores. See Citations and Thread Score.

Transaction. A signed instruction sent to Algorand. Every ARIADNE action is one or a few transactions that your wallet signs. See What is on the blockchain, and what is not.

Type. What kind of publication an article is: article, notes, amendment, dataset or replication. It is fixed at publication. See Articles and their statuses.

Under review. The status in which the author invites reviews. New versions are still allowed, and from here the author can close the article. See Get the Peer-reviewed seal.

Version. One state of an article’s content, numbered from 1, each with its own CID. New versions are possible while the article is a preprint or under review; earlier versions stay readable. See New versions, amendments and retraction.

Vote. An upvote for an article, for a review (Useful) or for a comment (Upvote). There are no downvotes; each person votes once per item and can never change or withdraw the vote. See Comment, mention and vote.

Vote weight. How much a vote, review recommendation or flag counts: 1 + ⌊√reputation⌋, from the voter’s reputation in the article’s primary field. Reputation 0 gives 1, 100 gives 11, 10 000 gives 101. See Reputation and vote weight.

Wallet. An app that holds your private key and signs your transactions. The web app connects to Pera, Defly and Lute; your wallet is your identity on ARIADNE. See Wallets and your address.

Zenodo. An open repository run by CERN. ARIADNE can prepare a draft of your article in your Zenodo account; you publish it there to get a DOI and a third preserved copy. On TestNet the Zenodo sandbox is used. See Get a DOI with Zenodo.