MétaCan
Menu
Back to cohort
Record W2011538429 · doi:10.1093/comjnl/bxu120

FEIPS: A Secure Fair-Exchange Payment System for Internet Transactions

2014· article· en· W2011538429 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueThe Computer Journal · 2014
Typearticle
Languageen
FieldComputer Science
TopicAdvanced Authentication Protocols Security
Canadian institutionsAthabasca University
Fundersnot available
KeywordsComputer securityPaymentConfidentialityComputer scienceAuthentication (law)Trusted third partyInternet privacyNon-repudiationThe InternetCryptographic protocolData exchangeProtocol (science)Payment systemCryptographyWorld Wide Web

Abstract

fetched live from OpenAlex

To be considered secure, a payment system needs to address a number of security issues. Besides fundamental security requirements, like confidentiality, data integrity, authentication and non-repudiation, another important requirement for a secure payment system is fair exchange. Many existing payment protocols require that customers must pay for products before their delivery (in the case of delivery of digital goods) or the delivery of the receipt (in the case of delivery of physical goods). This unfair situation should be eliminated afterward; that is, it is necessary to rebalance fairness for customers. To address these issues, we propose the Fair Exchange Internet Payment Protocol (FEIPS). The FEIPS protocol is designed for the payment of physical goods and falls into the category that uses a trusted third party for ensuring fair exchange. Although FEIPS has a strong emphasis on fair exchange, it still guarantees strong security properties, including confidentiality, data integrity, authentication and non-repudiation. The FEIPS protocol is designed to be simple and practical, unlike other similar protocols designed for the payment of physical goods. To demonstrate that FEIPS satisfies the desired properties, we perform a formal verification using the HLPSL language and the AVISPA tool.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.893
Threshold uncertainty score0.424

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0010.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.017
GPT teacher head0.258
Teacher spread0.240 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it