domains / families / research / financial-cryptography-and-data-security
financial-cryptography-and-data-security
separate
Use when targeting Financial Cryptography and Data Security (FC) or deciding whether a computer-science manuscript fits this venue. Encodes conference fit, framing, evidence bar, submission-cycle checks, rebuttal posture, and desk-reject risks for financial security.
When to use
- targeting Financial Cryptography and Data Security (FC)
- deciding whether a computer-science manuscript fits this venue
- conference fit, framing, evidence bar, submission-cycle checks
- rebuttal posture, and desk-reject risks for financial security
- financial cryptography, blockchain, digital assets, payment systems, economics, and security
- re-framing from journal style or arXiv style into a selective CS conference narrative
- evidence-gap, anonymity, artifact, rebuttal, or re-routing diagnosis
When not to use
- substitute for the current year's CFP, author kit, ethics policy, or submission portal
- generic CS paper without naming exact subcommunity, contribution type, and proof or empirical standard
- crypto hardware (route to CHES)
- privacy-first protocols or measurements (route to PETS)
- broad security (route to CCS/S&P/USENIX)
- empirical finance (route to economics/finance venues)
- general regional security (route to AsiaCCS)
Skill page
Source