Freelance Crypto Jobs: Find the Best Freelance Opportunities in Crypto

About Us

Chainlabs is a Web3 data analytics and software boutique specializing in blockchain intelligence. Our mission is to enhance Web3 analytics, combat illicit activities, and foster transparency in the crypto ecosystem. We work with AML service providers, analytics firms, and law enforcement globally.

Role Overview

We’re hiring a Germany-based Regional Web3 Researcher (part-time) to expand our understanding of Belarus's crypto ecosystem.

Ideal for students or professionals passionate about blockchain/Web3 who want impact, flexibility, and hands-on research experience. This role can qualify as an internship for academic credit (school approval required).

Why Join Us

- Contribute to meaningful work that improves blockchain transparency and fights illicit activity.
- Build skills across regional market research, fintech analysis, and blockchain fundamentals.
- Learn from an experienced Web3 investigations team and grow in a high-trust, remote environment.

Key Responsibilities

- Ecosystem Mapping (Germany): Track exchanges, OTC/P2P venues, social communities, payment rails (e.g., Interac e-Transfer/EFT), and growth trends.
- Regulatory Awareness: Summarize public developments relevant to Germany.
- Market Intelligence: Identify key influencers, forums, and local narratives; capture regional adoption drivers and risks.
- Source Building (OSINT): Collect and structure open-source data (Sheets) with clear citations and simple quality notes.
- Reporting: Produce short, action-oriented summaries and datasets that the tracing team can use immediately.

Requirements

- Strong interest in blockchain and Web3 technologies - Knowledge of regional cryptocurrency trends and marketing strategies.
- Proficiency in using research tools and Google Sheets.
- Excellent written and verbal communication skills in English, as well as German.
- Ability to work independently and meet deadlines.
- Students currently enrolled in university programs are encouraged to apply.
- Nice to have: familiarity with FINTRAC/CSA public materials, Interac/EFT rails, and crypto exchange mechanics.

What We Offer

- Flexible remote work (10–20 hrs/week, project-driven).
- Hourly compensation based on experience and output.
- Mentorship, training materials, and exposure to real Web3 investigations.
- Opportunity to grow into broader tracing/research responsibilities.

Security & Compliance (lightweight)

- Follow Chainlabs’ security practices (2FA, VPN, secure handling of sources).
- Complete a brief identity verification before access to internal systems.
- Respect privacy and data-minimization guidelines when collecting/storing information.

About Us

Chainlabs is a Web3 data analytics and software boutique specializing in blockchain intelligence. Our mission is to enhance Web3 analytics, combat illicit activities, and foster transparency in the crypto ecosystem. We work with AML service providers, analytics firms, and law enforcement globally.

Role Overview

We’re hiring a Germany-based Regional Web3 Researcher (part-time) to expand our understanding of Belarus's crypto ecosystem.

Ideal for students or professionals passionate about blockchain/Web3 who want impact, flexibility, and hands-on research experience. This role can qualify as an internship for academic credit (school approval required).

Why Join Us

- Contribute to meaningful work that improves blockchain transparency and fights illicit activity.
- Build skills across regional market research, fintech analysis, and blockchain fundamentals.
- Learn from an experienced Web3 investigations team and grow in a high-trust, remote environment.

Key Responsibilities

- Ecosystem Mapping (Germany): Track exchanges, OTC/P2P venues, social communities, payment rails (e.g., Interac e-Transfer/EFT), and growth trends.
- Regulatory Awareness: Summarize public developments relevant to Germany.
- Market Intelligence: Identify key influencers, forums, and local narratives; capture regional adoption drivers and risks.
- Source Building (OSINT): Collect and structure open-source data (Sheets) with clear citations and simple quality notes.
- Reporting: Produce short, action-oriented summaries and datasets that the tracing team can use immediately.

Requirements

- Strong interest in blockchain and Web3 technologies - Knowledge of regional cryptocurrency trends and marketing strategies.
- Proficiency in using research tools and Google Sheets.
- Excellent written and verbal communication skills in English, as well as German.
- Ability to work independently and meet deadlines.
- Students currently enrolled in university programs are encouraged to apply.
- Nice to have: familiarity with FINTRAC/CSA public materials, Interac/EFT rails, and crypto exchange mechanics.

What We Offer

- Flexible remote work (10–20 hrs/week, project-driven).
- Hourly compensation based on experience and output.
- Mentorship, training materials, and exposure to real Web3 investigations.
- Opportunity to grow into broader tracing/research responsibilities.

Security & Compliance (lightweight)

- Follow Chainlabs’ security practices (2FA, VPN, secure handling of sources).
- Complete a brief identity verification before access to internal systems.
- Respect privacy and data-minimization guidelines when collecting/storing information.

About Us

Chainlabs is a Web3 data analytics and software boutique specializing in blockchain intelligence. Our mission is to enhance Web3 analytics, combat illicit activities, and foster transparency in the crypto ecosystem. We work with AML service providers, analytics firms, and law enforcement globally.

Role Overview

We’re hiring a citizen from Hong Kong for our Regional Web3 Data Specialist (part-time) to expand our understanding of Hong Kong's crypto ecosystem.

Ideal for students or professionals passionate about blockchain/Web3 who want impact, flexibility, and hands-on research experience. This role can qualify as an internship for academic credit (school approval required).

Why Join Us

- Contribute to meaningful work that improves blockchain transparency and fights illicit activity.
- Build skills across regional market research, fintech analysis, and blockchain fundamentals.
- Learn from an experienced Web3 investigations team and grow in a high-trust, remote environment.

Key Responsibilities

- Ecosystem Mapping (Hong Kong): Track exchanges, OTC/P2P venues, social communities, payment rails (e.g., Interac e-Transfer/EFT), and growth trends.
- Regulatory Awareness: Summarize public developments relevant to Hong Kong.
- Market Intelligence: Identify key influencers, forums, and local narratives; capture regional adoption drivers and risks.
- Source Building (OSINT): Collect and structure open-source data (Sheets) with clear citations and simple quality notes.
- Reporting: Produce short, action-oriented summaries and datasets that the tracing team can use immediately.

Requirements

- Strong interest in blockchain and Web3 technologies - Knowledge of regional cryptocurrency trends and marketing strategies.
- Proficiency in using research tools and Google Sheets.
- Excellent written and verbal communication skills in English and Cantonese.
- Ability to work independently and meet deadlines.
- Students currently enrolled in university programs are encouraged to apply.
- Nice to have: familiarity with FINTRAC/CSA public materials, Interac/EFT rails, and crypto exchange mechanics.

What We Offer

- Flexible remote work (10–20 hrs/week, project-driven).
- Hourly compensation based on experience and output.
- Mentorship, training materials, and exposure to real Web3 investigations.
- Opportunity to grow into broader tracing/research responsibilities.

Security & Compliance (lightweight)

- Follow Chainlabs’ security practices (2FA, VPN, secure handling of sources).
- Complete a brief identity verification before access to internal systems.
- Respect privacy and data-minimization guidelines when collecting/storing information

About Us

Chainlabs is a Web3 data analytics and software boutique specializing in blockchain intelligence. Our mission is to enhance Web3 analytics, combat illicit activities, and foster transparency in the crypto ecosystem. We work with AML service providers, analytics firms, and law enforcement globally.

Role Overview

We’re hiring a Japan-based Regional Web3 Researcher (part-time) to expand our understanding of Japan's crypto ecosystem.

Ideal for students or professionals passionate about blockchain/Web3 who want impact, flexibility, and hands-on research experience. This role can qualify as an internship for academic credit (school approval required).

Why Join Us

- Contribute to meaningful work that improves blockchain transparency and fights illicit activity.
- Build skills across regional market research, fintech analysis, and blockchain fundamentals.
- Learn from an experienced Web3 investigations team and grow in a high-trust, remote environment.

Key Responsibilities

- Ecosystem Mapping (Japan): Track exchanges, OTC/P2P venues, social communities, payment rails (e.g., Interac e-Transfer/EFT), and growth trends.
- Regulatory Awareness: Summarize public developments relevant to Japan.
- Market Intelligence: Identify key influencers, forums, and local narratives; capture regional adoption drivers and risks.
- Source Building (OSINT): Collect and structure open-source data (Sheets) with clear citations and simple quality notes.
- Reporting: Produce short, action-oriented summaries and datasets that the tracing team can use immediately.

Requirements

- Strong interest in blockchain and Web3 technologies - Knowledge of regional cryptocurrency trends and marketing strategies.
- Proficiency in using research tools and Google Sheets.
- Excellent written and verbal communication skills in English and Japanese.
- Ability to work independently and meet deadlines.
- Students currently enrolled in university programs are encouraged to apply.
- Nice to have: familiarity with FINTRAC/CSA public materials, Interac/EFT rails, and crypto exchange mechanics.

What We Offer

- Flexible remote work (10–20 hrs/week, project-driven).
- Hourly compensation based on experience and output.
- Mentorship, training materials, and exposure to real Web3 investigations.
- Opportunity to grow into broader tracing/research responsibilities.

Security & Compliance (lightweight)

- Follow Chainlabs’ security practices (2FA, VPN, secure handling of sources).
- Complete a brief identity verification before access to internal systems.
- Respect privacy and data-minimization guidelines when collecting/storing information.

About Us

Chainlabs is a Web3 data analytics and software boutique specializing in blockchain intelligence. Our mission is to enhance Web3 analytics, combat illicit activities, and foster transparency in the crypto ecosystem. We work with AML service providers, analytics firms, and law enforcement globally.

Role Overview

We’re hiring a Kyrgyzstan-based Regional Web3 Researcher (part-time) to expand our understanding of Kyrgyzstan's crypto ecosystem.

Ideal for students or professionals passionate about blockchain/Web3 who want impact, flexibility, and hands-on research experience. This role can qualify as an internship for academic credit (school approval required).

Why Join Us

- Contribute to meaningful work that improves blockchain transparency and fights illicit activity.
- Build skills across regional market research, fintech analysis, and blockchain fundamentals.
- Learn from an experienced Web3 investigations team and grow in a high-trust, remote environment.

Key Responsibilities

- Ecosystem Mapping (Kyrgyzstan): Track exchanges, OTC/P2P venues, social communities, payment rails (e.g., Interac e-Transfer/EFT), and growth trends.
- Regulatory Awareness: Summarize public developments relevant to Kyrgyzstan.
- Market Intelligence: Identify key influencers, forums, and local narratives; capture regional adoption drivers and risks.
- Source Building (OSINT): Collect and structure open-source data (Sheets) with clear citations and simple quality notes.
- Reporting: Produce short, action-oriented summaries and datasets that the tracing team can use immediately.

Requirements

- Strong interest in blockchain and Web3 technologies - Knowledge of regional cryptocurrency trends and marketing strategies.
- Proficiency in using research tools and Google Sheets.
- Excellent written and verbal communication skills in English, Kyrgyz and if possible, Russian as well.
- Ability to work independently and meet deadlines.
- Students currently enrolled in university programs are encouraged to apply.
- Nice to have: familiarity with FINTRAC/CSA public materials, Interac/EFT rails, and crypto exchange mechanics.

What We Offer

- Flexible remote work (10–20 hrs/week, project-driven).
- Hourly compensation based on experience and output.
- Mentorship, training materials, and exposure to real Web3 investigations.
- Opportunity to grow into broader tracing/research responsibilities.

Security & Compliance (lightweight)

- Follow Chainlabs’ security practices (2FA, VPN, secure handling of sources).
- Complete a brief identity verification before access to internal systems.
- Respect privacy and data-minimization guidelines when collecting/storing information.

I’m looking for an experienced Unity developer to help complete the first playable demo of a multiplayer boat survival game currently in development.

The project has already been started in Unity and I will continue working on it while I search for the right developer. I am not looking for someone to start an entirely new project from scratch. I need someone who can review what has already been built, work from the existing project, troubleshoot where necessary, and efficiently complete what is still needed for the demo.

The core concept involves players navigating boats through increasingly dangerous storm conditions while dealing with environmental hazards and obstacles. For the first demo, the priority is creating a functional and believable gameplay experience with a controllable boat, convincing ocean movement and buoyancy, stormy weather and atmosphere, hazards or obstacles, and the core gameplay necessary to demonstrate the concept.

This first contract is specifically for the playable demo. It does not include blockchain or NFT integration. That portion of the project is being handled separately.

I am looking for someone who is very comfortable with Unity and C#, particularly someone with experience in water or ocean environments, boat physics and buoyancy, weather systems, gameplay mechanics, optimization, and troubleshooting existing Unity projects. Multiplayer experience is also highly preferred because the larger game is being designed as a multiplayer experience.

The fixed budget for this first demo milestone is $500 and the budget is firm. Please only apply if you are comfortable completing the agreed demo scope within this budget. Additional development may be offered as separate paid milestones if we work well together.

I am looking to move quickly. When applying, please include examples of Unity games or playable projects you have personally worked on, especially anything involving boats, water, physics, weather, survival gameplay, or multiplayer. Please also briefly explain what part of those projects you personally handled.

Good communication and the ability to work efficiently within an existing project are important.

We are building a financial tracking platform that processes 100K+ financial and crypto transactions per day, analyzes transaction activity, and triggers user-specific events and notifications in near real time.

We are looking for a senior FinTech engineer to help with an existing production codebase. The immediate task is to review a PR, identify the root cause of a bug, and implement or validate the fix.

What You'll Do
* Review an existing PR and related code.
* Debug and fix transaction-processing issues.
* Validate financial and crypto transaction logic.
* Check for concurrency, duplicate processing, and data consistency issues.
* Improve tests and confirm the fix is production-ready.

Tech Stack
* Python, FastAPI
* Vue.js, TypeScript
* SQL, Apache Iceberg
* OpenAI API, MCP
* Financial and crypto transaction data
* GitHub, CI/CD, automated PR review
* AI-assisted development workflows

What We're Looking For
Strong experience with Python, FastAPI, SQL, and production debugging is required.

Experience with FinTech, crypto, blockchain data, transaction processing, trading, portfolio tracking, or other high-volume financial systems is strongly preferred.

You should understand concepts such as idempotency, transaction reconciliation, event-driven processing, concurrency, financial precision, and data integrity.

To Apply
Please briefly describe your experience with:
* FinTech or crypto transaction systems
* Python / FastAPI
* High-volume transaction or data processing
* Debugging complex production issues

Please include one example of a difficult bug you diagnosed and fixed.

This is an initial PR review and bug-fix task, with potential for ongoing work if there is a strong fit.

We're a content marketing agency. Our client is a new association for Argentine freelancers, launching this year (the technical side is still in preparation — details in the interview).

Many Argentine freelancers get paid in crypto or hold savings in stablecoins — and don't fully understand what to do about it come tax time. We're looking for an accountant or tax advisor with real experience in crypto assets, to create a practical guide "Crypto Assets and Taxes for Freelancers" (in text, approx. 2,500–4,000 words).

A rough outline — but we're counting on your perspective: you know what people are actually asking about right now; the topic and angle are open to discussion:

- How crypto assets are classified in Argentina
- What to declare and when (Bienes Personales, Ganancias)
- Getting paid in crypto by foreign clients — how to handle it properly
- Stablecoins as savings — the legal framework
- Common mistakes and their consequences

The format is open: text, video, or audio — whatever's most comfortable. What matters most is that it's thorough, engaging, and accurate.

Important: the material must be strictly informational, within legal bounds, with a disclaimer. We need an expert who can explain how to do things correctly.

Terms are the same as in listing 1: our brief → your material → our style editing; published in the association's materials with your name, photo, and a link to your practice; budget USD 200–300; first draft in 10 days.

In your proposal: (1) 3–4 lines about your experience with clients who hold crypto assets, and the most common misconception you encounter; (2) a sample of your writing.

We are seeking a senior Web3 developer to help build and enhance our blockchain-based project. The ideal candidate will have strong experience with smart contracts, decentralized applications, and blockchain integration. You will work on developing secure, scalable solutions and collaborating with our team to deliver high-quality results. If you are passionate about blockchain technology and have a proven track record in Web3 development, we would love to hear from you.

We need a senior blockchain developer to help complete our decentralized platform development successfully. The role requires strong experience in both web development and blockchain technologies, including Solidity. You will work on key platform components, ensure reliable implementation, and support the project through completion. We are looking for someone who can contribute effectively, communicate clearly, and help deliver a successful outcome for the platform.

1-on-1 Futures Trading Coach Needed

I am seeking an experienced futures trading coach for personalised 1-on-1 mentorship.

I have 1–2 months of NY session trading experience and am committed to learning systematically.

I need to strengthen my understanding of market structure, price action, and technical analysis.

Key priorities include risk management, position sizing, entries/exits, and trade management.

I want to build a clear, repeatable trading plan and daily routine so I could build a career.

I am working to improve emotional discipline and reduce fear, greed, and overtrading.

I would value chart reviews, trade feedback, journaling guidance, and accountability.

Please have genuine futures-trading experience and a practical, education-focused coaching style.

Please share your coaching structure, availability, rates, and whether you offer an introductory call.

Seeking a skilled NFT artist to create distinctive digital collectibles. The ideal creator will design cohesive, visually striking pieces with strong thematic identity, attention to detail, and optimized formats for blockchain minting. Responsibilities include concept development, producing high-resolution artwork, preparing layered source files, and delivering web-ready assets with clear variation keys. Prior NFT or digital art experience is preferred; professionalism, adherence to deadlines, and creativity are essential.

Background

- ETF Copilot (etf-copilot.com) is an app helping US investors make better decisions when investing in ETFs - funds of stocks.
- I need one organized person, part-time and long-term, to own outreach and the research behind it. We will start with writing to three kinds of people: sites that recommend investing tools, US finance writers and newsletters, and independent financial advisors.
- I provide the lists, the templates, the data and free access to the product. You own the sending, the follow-through, and the research that keeps the lists full.
- Around 10 hours a week, ongoing.

Responsibilities

- Send outreach emails every working day — each written for the person receiving it, not a template with the name changed.
- Keep the conversations going: reply promptly, follow up once on schedule, never drop a thread.
- Check facts before anything goes out — contact still published, person still writes there, figure still current on our site.
- Keep the tracker accurate so I can open it and see where any conversation stands.
- Research and build target lists from a short brief: find the people, verify they're real and reachable, add them in the agreed format.
- Send me a short weekly summary — what went out, what came back, what you'd change.

Requirements

- Fluent, natural written English. Your emails are read by professional writers and advisors who delete templates on sight.
- Comfortable with finance and investing. You don't need to be an analyst, but you must be able to read a page about funds and see what's interesting on it.
- This is not a crypto, forex, CFD, gambling or betting work - the tone is the opposite of get-rich-quick, and your writing has to match.
- Very organized. You work from a tracker, hit dates, report weekly without being chased, and never lose a thread.
- Able to research on your own from a vague brief and come back with a qualified list.
- Comfortable with spreadsheet tracker (Excel or Google Sheets) and a task board (Trello or similar).

To apply

Answer all three. Write it yourself — AI-written proposals are obvious and I skip them.

1. Open etf-copilot.com and tell me in one sentence, in your own words, what it does and who should use it. Put this as the first line of your proposal.

2. Paste one outreach email you wrote that got a reply. Include who it went to and why you think it worked.

3. If I ask you to find US financial advisors who might use an ETF analysis tool with clients - where do you start, and how do you decide who is worth writing to? Do not do research, just describe how you would approach the task.

I need a licensed CPA, IRS Enrolled Agent, or attorney to review a small set of account records and sign a one-page letter of opinion confirming a $0 valuation for an IRA Grantor Trust. The trust previously held cash that was moved through a bank account into a cryptocurrency exchange, then fully liquidated and returned to the IRA custodial account. I need review of Solera and Kraken statements to confirm no remaining assets, plus a signed letter stating the trust’s fair market value is $0.00 as of a specified date. This is a narrow factual attestation, not complex legal or tax work. Please let me know if you can take this on, your fee, and expected turnaround time.

We are looking for a senior Wikipedia, entity authority and digital PR consultant to support an established Italian news and multimedia organization and its portfolio of vertical media brands.

This engagement consists of two clearly separated projects.

Project 1 — Wikipedia Eligibility & Page Development for Alanews

Alanews is an Italian news and multimedia agency founded in 2012, with more than 14 years of editorial activity.

The organization already has:

an established official website and registered news operation;
an existing Wikidata entity;
independent references and citations from major Italian media;
a long-standing professional relationship with ANSA;
an official ANSA Corporate reference to its partnership with the “Alanews Video Agency”;
content references and attribution from major outlets including ANSA, Corriere della Sera, Repubblica and Rai;
additional industry references and journalistic recognition.

We are looking for an experienced professional who can independently assess whether Alanews currently meets Wikipedia notability requirements.

Scope

The consultant should:

audit existing independent and reliable sources;
evaluate Wikipedia notability eligibility;
identify weaknesses or missing source coverage;
research additional high-quality independent secondary sources;
distinguish substantial coverage from simple mentions or content credits;
prepare a neutral, encyclopedic and properly sourced draft if eligibility is confirmed;
ensure correct Conflict of Interest disclosure and compliance;
recommend the safest draft/review/submission process;
support legitimate community review or revision requests;
review Wikidata and Wikimedia Commons consistency where relevant.

We are not looking for guaranteed publication, promotional editing or attempts to bypass Wikipedia policies.

The objective is a sustainable, policy-compliant Wikipedia presence only if notability is genuinely supported.

Project 2 — Digital Authority, Entity Authority & Backlink Strategy

Separately from Wikipedia, we want to build a long-term authority strategy for Alanews and our portfolio of editorial brands.

The media properties include:

Alanews — alanews.it
AlaTV — tv.alanews.it
NewzGen — newzgen.it
SaluteWeb — saluteweb.it
OkViaggi — okviaggi.it
VinaMundi — vinamundi.it
CryptoHack — cryptohack.it

Not every brand needs or should have a Wikipedia page.

The goal is instead to strengthen each property's independent authority, entity recognition, editorial credibility and high-quality external footprint.

Entity Authority Scope

We would like an audit and strategy covering areas such as:

Wikidata eligibility and optimization;
Wikimedia Commons where appropriate;
Knowledge Graph/entity consistency;
authoritative media and industry databases;
trusted directories;
organization and publisher entity consistency;
ownership and brand relationship signals;
editorial attribution consistency;
independent third-party citations;
missing or incorrect profiles;
author/publisher authority signals;
industry-specific authority opportunities;
brand mentions and unlinked citations;
entity relationships between TechMedia Group, Alanews and individual vertical brands.

We also want guidance on where brands should be connected and where they should remain independently positioned.

We specifically want to avoid creating an artificial network footprint.

High-Quality Backlink & Digital PR Strategy

A major component of Project 2 will be the development of a high-level backlink and digital PR strategy.

We are not interested in:

PBNs;
bulk backlink packages;
automated links;
low-quality guest-post networks;
spam directories;
artificial link exchanges;
mass sponsored placements;
tactics that create Google penalty or reputational risk.

We are interested in earning or developing links and citations from:

major media organizations;
highly authoritative editorial websites;
institutional websites;
universities and research organizations;
professional associations;
industry bodies and databases;
relevant specialized publications;
high-quality editorial partnerships;
legitimate syndication opportunities;
journalist and source databases;
expert contributions;
interviews;
original research and data-led content;
digital PR campaigns;
high-value unlinked mention reclamation.

For proposed backlink opportunities, we would like visibility into:

target domain;
topical relevance;
authority/trust level;
editorial quality;
acquisition method;
whether the placement is earned, contributed, partnership-based or sponsored;
difficulty;
strategic value;
potential SEO or reputational risk.

Our main KPI is not backlink volume.

We care much more about:

quality of referring domains;
topical authority;
entity authority;
trusted editorial citations;
independent mentions;
source diversity;
brand recognition;
long-term search and knowledge-graph credibility.
Deliverables

The first phase should ideally produce:

Alanews Wikipedia notability audit.
Source inventory with quality classification.
Wikipedia GO / HOLD / NO-GO recommendation.
Identification of missing source coverage.
Wikipedia draft and submission strategy if eligible.
Entity authority audit for Alanews.
Entity/authority assessment for each vertical media brand.
Authority gap analysis.
High-quality backlink and digital PR strategy.
Prioritized target/source list.
Risk assessment for proposed tactics.
Recommended 6–12 month roadmap.
Ideal Candidate

We are looking for someone with proven senior experience in one or more of the following areas:

Wikipedia editing and notability assessment;
Wikipedia Conflict of Interest compliance;
Wikidata;
Wikimedia ecosystem;
entity SEO;
Google Knowledge Graph;
digital PR;
high-authority link acquisition;
media/brand reputation;
publisher or news-industry SEO.

Experience with news organizations, publishers, media companies or complex brand portfolios is highly desirable.

When Applying

Please include:

your experience with Wikipedia notability assessments;
examples of comparable company/media projects;
your approach to Conflict of Interest;
your methodology for entity authority;
your approach to high-quality backlink acquisition;
examples of the types of authoritative sources you normally target;
how you keep Wikipedia work completely separate from SEO/backlink activity;
whether you can personally handle both projects;
recommended project phases;
estimated cost for each project or workstream.

Please do not apply if your approach relies primarily on selling backlink packages or guaranteeing Wikipedia publication.

We are looking for a long-term, high-quality authority project, not simply a Wikipedia page or a backlink campaign.

Meta Earth is a next-gen modular blockchain ecosystem with native KYC-enabled DID, and ME Pass is the app where users can create their wallet. We’re looking for KOLs and app users to help promote the ME Pass App through a refer-to-earn affiliate campaign. The goal is to grow awareness, drive downloads, and increase user engagement. Ideal candidates should have a strong social media presence and be able to share the app with their audience in a meaningful way.

We are hiring a senior Frontend Engineer (React / TypeScript) for Quay ($QUAY) — a USDC-backed crypto card moving from MVP to production.

This is not a junior role, not a “build a landing page,” and not a “rewrite everything in Next.js in week one” gig. You will own the web client: keep the existing token dApp working, and add the card product UI.

ABOUT THE PRODUCT
Quay is a USDC-backed crypto card. Users will hold a spendable USD balance, pass KYC, receive a virtual card, and spend at merchants. $QUAY is the token. The blockchain is NOT the card ledger. Card spend, available balance, freeze, and authorization live in a Go API + PostgreSQL ledger. The React app talks to that API for card flows. Wallet connect stays for deposits and proving ownership.

First product milestone (everyone on this project is hired against this sentence):
a sandbox virtual card that can be frozen and that declines when available balance is insufficient.

WHAT EXISTS TODAY (you will inherit this)
A React 18 + TypeScript dApp (Create React App + react-app-rewired):
- Wallet connect (MetaMask / WalletConnect)
- Dashboard: locked / unlocked / total $QUAY, market stats
- Uniswap V3 swap ($QUAY + convenience fee)
- Provide liquidity (USDT–WETH, WETH–QUAY), stake / unstake, rewards
- Buy crypto via Transak
- Token vesting: schedules, claim, withdraw
- Legal pages (terms, privacy, cookies) and a first-visit disclaimer

Stack you will actually touch:
React 18, TypeScript, React Router 5, Tailwind CSS, styled-components, ethers 5, @usedapp/core, Web3Modal, WalletConnect, Uniswap V3 SDK/widgets, Transak, Axios, Jest (utils only today), Node 16 / CRA.

Known constraints (you may mention them; we already know them):
- Main screen is tab state, not real URLs
- WalletConnect v1 and Goerli are obsolete
- Some “hooks” are async functions, not React hooks
- Tests cover formatting/vesting utils, not UI or chain calls
- REACT_APP_* values are public — treat them that way

WHAT YOU WILL OWN
- Card product UI: KYC status, available balance, virtual card surface, freeze/unfreeze, transaction list
- Routing and information architecture: wallet-first surfaces (swap, LP, vest) vs session/API-first surfaces (KYC, card, txs)
- Auth UX: logged-out vs no-wallet vs KYC-pending vs KYC-rejected vs card-ready
- Loading, error, empty, and blocked states (wrong network, pending tx, frozen card, insufficient card balance, KYC rejected)
- Safe integration of an issuer widget for card reveal — our UI never collects PAN/CVV
- Talk to the Quay Go API for all card flows (mocked at first, real later)
- Keep swap / LP / vesting working while card routes land
- Senior judgment on what to migrate now (WC v1, routing, tests) vs what to leave until the card MVP exists
- Work with a Go backend engineer and a Solidity engineer; you do not replace them

HARD RULES (automatic no if you fight these)
- Never put issuer, KYC, or custody secrets in the React bundle
- Never add PAN/CVV fields, store card numbers, or log PII
- Card available balance is not on-chain and not a number you invent in localStorage
- Do not rebuild Uniswap
- Do not move the project to Solana
- Do not propose a full rewrite as week-one work unless you can justify it against the card milestone

MUST-HAVE EXPERIENCE
- Production React + TypeScript shipped to real users (not only tutorials / student apps / Figma-to-HTML)
- REST (or similar) API clients: auth session, loading/error, optimistic UI without double-submit
- Component architecture that can grow (routing, state, not a 3,000-line page)
- Clear written English (you will write a short design before a big UI change)
- Comfortable in an existing codebase (CRA, mixed Tailwind + styled-components) — you improve it, you do not sneer at it

NICE TO HAVE
- Wallet UX (MetaMask, WalletConnect, wrong-network, pending tx)
- Fintech / KYC / payments / card dashboards
- ethers.js or similar
- Accessibility (keyboard, labels, disabled states that explain why)
- Replacing CRA/Vite/Next only when it serves the milestone
- Tests for UI that talks to APIs (and optionally chain)

OUT OF SCOPE FOR THIS SEAT
- Solidity / protocol design
- Go ledger / issuer webhooks (you consume the API)
- Real issuer SDK or real KYC vendor in the take-home
- Visual branding overhaul before freeze/KYC states work

ENGAGEMENT
- Start: as soon as the right person is available
- Rate: typically $100–$120/hr depending on scope and seniority
- Full-time preferred; part-time welcome if you have other commitments
- Remote
- Next step after a strong proposal: a paid, timeboxed technical assessment (short design + a small mocked Card dashboard), then a 60–75 min walkthrough

HOW TO APPLY
Proposals that do not answer the questions below will be declined. Keep it short. Do not send a generic “I can develop React websites” pitch, a list of every UI library you have seen, or an AI wall of text.

I am seeking a professional OSINT / digital forensics investigator for an ongoing social media impersonation and suspected fraud matter involving my public identity and business.

BACKGROUND

I am a business owner and TikTok creator publicly known as Supreme Empress Cherita. I have been dealing with an ongoing and serious impersonation problem since 2024 involving multiple TikTok accounts.

This is not a recent or isolated incident. Different accounts have impersonated me at different times over approximately two years.

AS OF RIGHT NOW, there are FOUR ACTIVE TikTok accounts that are openly impersonating me and are still using my name.

However, these are not the only accounts that have been involved.

There have been additional TikTok accounts that previously used my identity, name, photographs, videos, content, or other identifying information. Some of those accounts later changed their names/usernames to something completely different and removed my videos and other content from their profiles.

Because those accounts changed their identities and removed my content, they may no longer appear at first glance to be impersonating me. However, I have reason to believe some may be connected to the same ongoing activity.

I would therefore like the investigation to consider both the FOUR CURRENTLY ACTIVE ACCOUNTS and the historical impersonation activity dating back to 2024 where evidence remains lawfully and reasonably available.

CURRENT TAKEDOWN PROCESS

I have already hired a separate professional takedown service that is working with TikTok to have the four currently active impersonation accounts removed.

I am NOT hiring an investigator primarily to perform account takedowns. The takedown process is already underway.

Because of that, the four currently active accounts could disappear at any time. Preserving publicly available evidence from those accounts before they are removed is extremely important.

WHAT HAS BEEN HAPPENING

This situation goes beyond someone simply copying my TikTok profile.

The impersonators have allegedly used my name, public identity, business identity, photographs, videos, and content while pretending to be me.

They have also allegedly communicated with people while representing themselves as me and directed people away from TikTok to communicate or conduct transactions through other services.

The information I have collected includes:

• Four currently active TikTok accounts openly impersonating me
• Information concerning additional TikTok accounts that previously impersonated me but later changed their names/usernames and removed my content
• Current and previous usernames that I have been able to document
• Phone numbers, including numbers that appear to be TextFree/VoIP numbers
• Email addresses created to resemble my legitimate email address, sometimes differing from my real email address by only one letter
• WhatsApp contact information
• Signal contact information
• Cash App/payment information
• Apple Pay/payment information
• Screenshots of conversations and communications involving the impersonators
• Screenshots and other evidence concerning impersonation accounts
• My legitimate TikTok account for comparison
• Other information and evidence collected from the impersonators and from people they have contacted

Some of the impersonators appear to have attempted to obtain money from people while pretending to be me.

MY PRIMARY OBJECTIVE

I am looking for an INVESTIGATION, not simply account removal.

My primary goal is to determine WHO is actually behind this activity.

I want to determine whether:

• The four currently active TikTok accounts are connected to one another
• The older accounts that previously impersonated me are connected to the current accounts
• The different phone numbers, emails, usernames, payment identifiers, and other information are connected
• The activity appears to originate from one person, multiple people, or a coordinated group
• There are cross-platform connections between the different identifiers
• The person or people responsible can reasonably be identified through lawful OSINT and investigative methods

I understand that identifying an anonymous account operator cannot be guaranteed.

I am looking for a professional investigator who will distinguish between what can actually be proven, what is strongly supported by evidence, and what is merely possible.

CROSS-PLATFORM INVESTIGATION

I would like the investigator to examine lawful and publicly available connections involving, where applicable:

• TikTok accounts
• Current usernames
• Previous usernames where discoverable
• Aliases
• Phone numbers
• TextFree/VoIP numbers
• Email addresses
• Look-alike email addresses
• WhatsApp information
• Signal information
• Cash App/payment identifiers
• Apple Pay/payment information
• Profile photographs
• Reused photographs
• Reused videos
• Posting patterns
• Communication patterns
• Profile/account histories
• Historical information dating back to 2024 where lawfully and reasonably available
• Publicly available metadata where legitimately available
• Cross-platform profiles and identifiers
• Other lawful digital indicators that could establish connections between the accounts

For example, if the same username, alias, phone number, email address, payment identifier, photograph, video, wording, contact information, posting behavior, or another identifier appears across multiple accounts or platforms, I would like that connection investigated and documented.

OLDER ACCOUNTS THAT CHANGED THEIR IDENTITIES

The older accounts are particularly important to me.

Some accounts that previously impersonated me later changed their names/usernames to something completely different and removed my videos/content.

I would like the investigator to determine, where reasonably possible, whether historical or publicly available evidence can document that these accounts previously impersonated me and whether those accounts can be connected to the currently active accounts or the same operator(s).

Because this activity has been occurring since 2024, recurring patterns across accounts and time periods may also be relevant.

EVIDENCE PRESERVATION

The four currently active TikTok accounts are already subject to professional takedown requests.

I therefore need the investigator to tell me how quickly evidence from the currently active profiles can be preserved before those accounts potentially disappear.

I would like appropriate publicly available evidence documented, including relevant URLs, usernames, profile information, dates/times where available, screenshots, and other relevant information that may assist in establishing what existed before removal.

QUESTIONS I NEED ANSWERED BEFORE HIRING

1. Can you investigate ALL FOUR currently active TikTok impersonation accounts together rather than analyzing only one profile?

2. Can you examine additional accounts that previously impersonated me but later changed their names/usernames and removed my videos/content?

3. Since this has been occurring since 2024, can you examine historical information that remains lawfully and reasonably available for connections between older and current accounts?

4. Can you determine whether the older accounts appear connected to any of the four currently active accounts?

5. Can you examine the associated phone numbers, including possible TextFree/VoIP numbers, for lawful and publicly available connections to usernames, accounts, services, aliases, or identities?

6. Can you examine the look-alike email addresses for connections to other publicly available accounts, usernames, websites, profiles, aliases, or identities?

7. Can you examine the WhatsApp and Signal information I have collected for lawful investigative leads or connections?

8. Can you examine Cash App/payment identifiers, Apple Pay information, and other payment information for publicly available connections to names, usernames, aliases, accounts, or other identifiers?

9. Can you perform cross-platform analysis to determine whether the activity appears to involve the same individual, multiple individuals, or a coordinated group?

10. Can you examine usernames, previous usernames where discoverable, aliases, posting behavior, profile history, reused content, connections, and publicly available metadata where legitimately available?

11. Can you compare activity and identifiers from 2024 to the present for recurring patterns that could connect accounts?

12. If attribution is realistically possible using lawful and publicly available information, can you attempt to identify the actual person or people responsible?

13. Can you preserve evidence from all four currently active TikTok accounts BEFORE they are removed?

14. Can you document whatever evidence remains concerning older accounts that changed their names and removed my content?

15. Will you document HOW accounts or identifiers are connected rather than simply providing an opinion?

16. Will I receive a WRITTEN INVESTIGATIVE REPORT containing the findings and supporting evidence?

17. Will that report clearly distinguish between CONFIRMED findings, strongly supported connections, and POSSIBLE/unconfirmed connections?

18. If a possible individual is identified, will the report explain the evidence supporting that attribution?

19. If conclusive identification is not possible, will the report still document useful evidence, connections, and investigative leads that could potentially be provided to an attorney or law enforcement?

20. If conclusive identification would require private records from TikTok, a telecommunications/VoIP provider, email provider, payment company, or another service, will the report explain what additional information or appropriate legal process would likely be required?

21. Because the four currently active accounts are pending removal, how quickly could evidence preservation begin?

22. What would the TOTAL PRICE be for the agreed scope?

BUDGET AND AFFORDABILITY

Affordability is extremely important to me. I am currently working with a limited budget, so I am specifically looking for the MOST AFFORDABLE way to have a meaningful and professional investigation completed.

I understand that professional investigative work has a cost, and I am not asking for free services. However, I need an option that is reasonably priced and focuses first on the evidence and investigative steps most likely to produce useful results.

I am NOT looking for an open-ended investigation, a large retainer, or unexpected additional charges.

I would strongly prefer a FIXED PRICE for a clearly defined first phase so that I know exactly what I will be paying before any investigation begins.

If everything described in this job cannot reasonably be completed within an affordable first phase, please recommend the MOST COST-EFFECTIVE approach for my situation rather than simply quoting me for the largest possible investigation.

My immediate priority is preserving and investigating the four currently active TikTok accounts and cross-referencing the phone numbers, VoIP numbers, email addresses, usernames, WhatsApp/Signal information, payment information, and other evidence I already possess.

Before hiring, I would like to know:

• Exactly what will be investigated
• How many accounts will be included
• Which identifiers will be examined
• Whether evidence preservation is included
• Whether cross-platform correlation is included
• Whether historical account research is included
• Whether a written investigative report is included
• The expected turnaround time
• The TOTAL FIXED PRICE
• Whether you can offer a lower-cost first phase focused on the strongest investigative leads
• Any circumstances that could result in additional charges

If investigating every historical account going back to 2024 immediately would substantially increase the cost, I am completely comfortable beginning with a smaller and more affordable first phase and expanding the investigation later only if the initial findings justify the additional expense.

PRIORITIES FOR THE FIRST PHASE

My priorities are:

1. Preserve publicly available evidence from the four currently active TikTok impersonation accounts before they disappear.

2. Investigate those four active accounts and the identifiers I already have associated with them.

3. Determine whether the four active accounts appear connected to one another.

4. Cross-reference the phone numbers, VoIP numbers, look-alike emails, WhatsApp/Signal information, payment identifiers, usernames, and other available evidence.

5. Attempt to identify the person or people responsible where the evidence reasonably permits.

6. Examine whether older accounts that changed their names and removed my content connect to the current accounts or the same operator(s).

7. Examine historical patterns dating back to 2024 where evidence remains available.

8. Produce a written investigative report documenting the evidence, methodology, findings, connections, and appropriate confidence level of the conclusions.

IMPORTANT LIMITATIONS AND EXPECTATIONS

I understand that an OSINT/private investigation cannot guarantee identification of an anonymous individual.

I also understand that certain information held privately by TikTok, telecommunications/VoIP providers, email providers, payment companies, and other platforms may require subpoenas, warrants, court orders, or other appropriate legal process and may not be obtainable through OSINT.

I am NOT requesting hacking, unauthorized access to accounts, password acquisition, unlawful surveillance, or any other unauthorized activity.

I am seeking a lawful, professional OSINT/digital investigation based on information I already possess and other information that can legitimately be obtained.

If the evidence reaches a point where further identification requires information that only a platform/provider possesses, I would like that limitation clearly documented so I understand what an attorney or law enforcement agency may need to pursue next.

TIME SENSITIVITY

This matter is time-sensitive because the four currently active impersonation accounts are already undergoing a professional takedown process.

I would therefore like evidence preservation from those four accounts to begin as quickly as reasonably possible after an agreement is reached.

Please respond with what you believe can realistically be accomplished, what you recommend for the most affordable and useful first phase, how quickly evidence preservation can begin, what deliverables I would receive, and the TOTAL FIXED COST before I proceed.

Professional Logo Refinement & Vector Brand Identity – UK Accountancy Firm

About the project:

Omega Centauri Advisors is a newly established UK accountancy and business advisory practice providing accounting, tax and advisory services to SMEs.

I already have a strong, approved creative direction for the brand identity, which will be supplied as a visual reference. I am not looking for a completely new logo or a broad branding exercise.

I am looking for an experienced brand/logo designer to take the existing concept and professionally reconstruct, refine and resolve it as an original, production-quality vector identity suitable for long-term commercial use.

The existing concept

The identity uses a restrained celestial device based around:

a central star;
an orbital form;
a small number of asymmetric surrounding points/stars, subtly referencing Omega Centauri as a stellar cluster;
a clean, widely spaced OMEGA CENTAURI wordmark;
ADVISORS as the secondary line;
Accounting · Tax · Advisory as the service descriptor.

There is no slogan or marketing tagline.

The astronomical reference should remain subtle and sophisticated. The firm must look like a high-quality UK professional-services practice — not a space company, technology startup, cryptocurrency brand, gaming business or luxury wealth manager.

What I want refined:

The supplied concept establishes the direction, but I want the designer to apply professional judgement to:

geometry and optical balance of the star/orbit device;
further simplification of the small surrounding cluster where appropriate;
typography, kerning and tracking;
proportions and spacing between device and wordmark;
exact colour values;
reproduction at small sizes;
monochrome performance.

The current concept uses Montserrat as an indicative direction only. I am not wedded to Montserrat. Please recommend the typeface that best achieves a clean, modern, understated and professional character. Any commercial font/licensing requirements must be identified.

Likewise, the current navy/teal/charcoal/off-white palette is directional rather than immutable. Teal should remain a restrained accent rather than becoming a dominant brand colour.

Required logo system:

The final identity should include:

Primary stacked logo
Horizontal logo
Compact OCA mark
Standalone device
Full-colour versions for light and dark backgrounds
Black/monochrome version
White/reversed version
Favicon/small-size version

The service descriptor Accounting · Tax · Advisory can be omitted from smaller variants where required for legibility.

Deliverables:

Final files should include:

editable vector master (.AI or equivalent)
SVG
EPS
vector PDF
transparent PNG exports
appropriate JPG exports
favicon/web assets
RGB and CMYK versions
monochrome versions
concise brand identity guide covering colours, typography, clear space, minimum sizes and basic usage.

Originality and ownership:

The supplied concept sheet was produced using generative AI and is provided solely as creative direction/reference material.

I do not want it simply image-traced or mechanically vectorised.

The successful designer should create fresh, professionally constructed vector artwork based on the approved direction, applying their own design judgement to geometry, typography, spacing and execution.

No stock logos, stock vectors or third-party graphical elements should be incorporated where exclusive rights cannot be transferred.

Upon final payment, all rights in the commissioned final artwork should be assigned to Omega Centauri Advisors Ltd, subject only to any separately identified third-party font licences.

The finished artwork needs to be suitable for commercial use and potential trademark registration.

Process:

I envisage:

Stage 1 — refined vector interpretation of the supplied direction, perhaps with 2–3 subtle refinements rather than unrelated alternative concepts.
Stage 2 — agree final device, typography, spacing and colours.
Stage 3 — create/test the complete logo system.
Stage 4 — final asset pack and concise brand guide.

When applying

Please include examples of restrained corporate/professional-services brand identities from your portfolio.

I'd also like you to answer one question:

Looking at the supplied concept, what are the first 2–3 things you would refine before turning it into the final professional identity?

I'm particularly interested in designers with strong typography and vector-logo skills. I'm looking for thoughtful refinement and craft rather than wholesale reinvention.

Middle Finger Money® is looking for an apparel graphic designer who wants to help build a brand — not simply decorate T-shirts.

We are developing an aspirational streetwear/lifestyle label built around success, confidence, choice and independence.

Our core idea is simple:

Money isn't freedom. Money gives you choices.

Middle Finger Money represents reaching — or working toward — the point where you have enough success and confidence to chart your own path, make your own decisions and live life on your terms.

We already have the brand positioning, website, product direction and creative brief. What we need now is a designer who can help create the visual language people eventually recognize as MFM.

What we're looking for

We want someone with genuine experience in:

Streetwear and fashion apparel graphics
Premium/luxury casualwear
Typography and wordmark treatments
Graphic tees and hoodies
Embroidery and small-format branding
Crests, badges, monograms or repeatable brand marks
Women's fashion/lifestyle apparel
Apparel production artwork
Building a cohesive visual system across a collection

Our references include brands such as:

Psycho Bunny
Billionaire Boys Club / ICECREAM
A Bathing Ape
Famous Stars and Straps
Adanola
Djerf Avenue
Young & Reckless

We are not looking to copy these brands. We are interested in how they create recognizable visual codes, desirable products, repeatable brand assets and a strong lifestyle around the clothing.

The MFM aesthetic

Think:

Established taste × self-made confidence

Private club × street culture

Old-money cues × modern ambition

Financial engraving × controlled street graphics

Monaco × Los Angeles

MFM should feel completely credible at an international Formula 1 weekend without becoming an automotive clothing brand.

Our primary customer is roughly 18–35, with a more restrained premium side of the collection that can comfortably extend into the 35–50+ customer.

Men's and women's apparel are both important.

Very important brand boundaries

The name itself provides the attitude.

We do not use:

Profanity
“FU” or coded profanity
Actual middle-finger imagery
Hand gestures suggesting a middle finger
Vulgar or obscene imagery
Cheap shock graphics
Drug imagery
Novelty-shirt humor
Crypto-bro / money-meme aesthetics
Generic print-on-demand artwork

If your first design instinct is to draw a hand giving the middle finger, this will not be the right project.

The goal is:

Provocative enough to be memorable.
Premium enough to be respected.

Production

Our apparel production partner is Apliiq.

Designs must therefore be created with real apparel production in mind, including methods such as:

Screen printing
DTG / digital printing
Embroidery
Woven labels
Patches
Front / back / sleeve placements

We are specifically interested in designers who understand that an embroidery design, a screen-print graphic and a full-color digital print require different creative approaches.

Final approved artwork must include properly organized production-ready files such as Adobe Illustrator/vector artwork, layered source files where appropriate, transparent PNG exports and placement/specification information.

This is initially a paid audition

Rather than selecting someone based solely on a portfolio, we plan to invite a small number of designers to complete the same paid mini-capsule exercise.

The test assignment will likely include:

One bold MFM graphic tee aimed at the 18–35 customer
One restrained premium MFM concept
One women's MFM concept
One proposed repeatable MFM visual device, such as a typography system, monogram, crest, pattern or other house code

We will provide our MFM Creative Direction deck.

This is paid work. We are not asking candidates to create speculative free designs.

The designer whose work best understands the brand will be considered for an ongoing relationship developing the first MFM collection and future drops.

Longer-term opportunity

The successful designer may help develop:

Core MFM apparel
Limited drops
Women's collections
Premium / restrained pieces
Hoodies and outerwear
Hats and embroidery
Motorsport-inspired capsules
Patterns and repeat graphics
Packaging and labeling
Seasonal collections
Collaborations

Our goal is to create a recognizable apparel brand — not a catalog of disconnected T-shirt graphics.

When applying

Please do not send your entire portfolio.

Instead, send us the five pieces or projects you have created that make you believe you understand Middle Finger Money.

For each, briefly tell us why you chose it.

Please also answer:

1. What apparel/streetwear brands do you believe currently do an exceptional job creating recognizable brand identity through clothing? Why?

2. Tell us about a brand or apparel collection where you created more than a single logo or graphic. What repeatable visual system did you help build?

3. What experience do you have preparing artwork for screen printing, embroidery and garment production?

4. Are you comfortable designing both expressive graphic pieces and restrained premium pieces within the same brand?

5. What is your preferred software and what editable source files do you normally deliver?

Please begin your proposal with:

“Money gives you choices.”

That lets us know you actually read the brief.

What will get our attention

We are especially interested in portfolios showing:

Premium streetwear
Fashion/lifestyle brands
Exceptional typography
Apparel graphics that feel genuinely wearable
Embroidery/badge/monogram systems
Women's lifestyle apparel
Strong art direction
Work that looks commercially viable rather than simply visually interesting

We are looking for someone who sees the opportunity to help create the visual language of Middle Finger Money, not just someone who can make us a cool shirt.

Website: middlefingermoney.com

Full-Cycle Sales / Business Development — Web3 Marketing

We’re looking for a hands-on salesperson to help grow a fast-growing creator marketing business working with companies across Web3.

This is a full-cycle sales role. We are not looking for someone who only does lead generation or appointment setting.

You’ll be responsible for identifying potential clients, starting conversations, running discovery calls, building proposals, following up and ultimately closing new business.

Our typical initial deals are around £3k–£15k, with significant opportunity for repeat business and increasing client spend.

What you’ll be doing

* Research and identify prospective clients within our target markets
* Prioritise the strongest commercial opportunities
* Generate your own pipeline through X, Telegram, Discord, email, LinkedIn and referrals
* Run discovery and sales calls
* Build proposals around client objectives
* Follow up and close new business
* Manage opportunities and activity through our CRM
* Develop existing clients into repeat customers
* Help us refine our ICP, messaging, pricing and sales process

Who we’re looking for

You should have experience personally sourcing and closing B2B deals, ideally within SaaS, marketing, advertising, creator/influencer marketing, MarTech or Web3.

Web3 experience is a strong advantage, but not essential. More important is that you understand digital marketing, are comfortable with hands-on outbound prospecting and can operate effectively in a small, fast-moving business.

We’re particularly interested in people used to shorter sales cycles and relatively high deal volume. This is unlikely to suit someone whose experience is primarily large enterprise deals with 6–12 month sales cycles.

About the opportunity

We’re a small team and growing quickly. You’ll work directly with the founders and have significant input into how we build our sales function.

We’re looking to start at approximately 15–20 hours per week, with the opportunity to increase the commitment substantially if things work well.

Good overlap with UK working hours is important.

When applying, please answer the following:

1. Tell us about the last three B2B deals you personally sourced and closed. What was the approximate deal value, how did you find the prospect, and how long did each take to close?
2. Roughly what percentage of your recent pipeline have you generated yourself versus receiving through inbound leads or SDRs?
3. Which outbound channels have you personally used? Please include any experience with X, Telegram or Discord.
4. Have you sold marketing, advertising, SaaS or Web3 services before? What did you sell and who were the typical buyers?

We’re looking for a Web3 Game Developer to join our team and help build a browser-based Web3 game.
You’ll work on gameplay, Three.js/WebGL, Web3 wallet integration, and blockchain features. Experience with JavaScript/TypeScript, Three.js, ethers.js, and EVM networks is preferred.
We’re looking for someone who has real game development experience, not just blockchain experience.

Please share your previous game/Web3 projects, GitHub or portfolio, availability, and hourly rate.

Potential for a long-term collaboration if the initial work goes well.

Can you make 10 seconds feel like a real startup launch?

We're an early-stage startup looking for a creative, hands-on AI video maker who knows Higgsfield and has a good eye for editing, pacing and sound. The first project is a short, cinematic launch/pre-launch teaser — around 10 seconds. I'll provide the base script and direction; I'd welcome your ideas on adapting it into something that actually works on screen.

The look: minimal, precise, physical and premium. Think industrial textures, real materials and restrained motion, rather than generic AI effects, spinning coins or crypto hype. A few excellent shots matter more than a complicated production.

FIRST PAID PILOT
• Adapt the supplied script into a concise shot plan before generating.
• Create and edit one approximately 10-second teaser, using Higgsfield as the main generation tool.
• Add clean titles and suitable sound/music, using assets cleared for commercial use.
• Deliver a 16:9 MP4 plus editable project files and usable source clips; keep framing suitable for a later vertical version.
• Include one focused revision round within the agreed concept.

THE HANDOVER MATTERS
Please provide the actual prompts, model/preset/settings, references where shareable, and brief notes on what worked. We'd like a reusable prompt pack and a simple step-by-step workflow we can repeat. A reusable Markdown AI-agent skill would be a welcome bonus; no coding or automation build is required for this first pilot.

BUDGET & COLLABORATION
This is a lean startup project with an initial target of $100 fixed-price. Please suggest a realistic scope and quote, including any generation-credit or licensed-asset costs. We are happy to keep the first concept simple to fit the budget. No purchases or extras without agreement.

Independent creators and newer freelancers with strong examples are welcome. Clear communication, creative judgement and a useful handover matter more than a long agency pitch. If the pilot works well, there may be occasional teasers, demo clips and social edits over the coming months, with scope and payment agreed separately.

TO APPLY
Send 1–3 relevant examples (ideally made with Higgsfield), tell us what you personally did, and include your fixed-price quote, estimated turnaround and whether you can provide the reusable prompts/workflow. Please flag what your quote includes for generation credits and revisions.

No custom unpaid sample is needed — existing work is enough. We'll share the script and detailed brand brief with the selected creator.

We’re looking for an experienced legal, compliance, or regulatory consultant to support Vizient on a range of strategic projects involving healthcare, technology, commercial contracts, corporate governance, and regulatory matters.

This is a project-based consulting engagement. We’re open to specialists with strong experience in a particular area rather than expecting one person to cover everything.

The work may include:

— Reviewing and negotiating commercial, technology, vendor, partnership, privacy, and AI-related agreements
— Advising on corporate structure, governance, entity matters, and strategic transactions
— Conducting regulatory research and identifying legal/compliance risks for new products or business initiatives
— Developing or reviewing compliance programs, policies, controls, and risk frameworks
— Advising on privacy, data protection, healthcare regulatory, and cross-border requirements
— Supporting KYC/KYB, AML, sanctions, transaction monitoring, or related compliance programs where applicable
— Performing compliance gap assessments and preparing organizations for audits or regulatory reviews
— Advising on technology, SaaS, AI governance, and enterprise risk matters
— Preparing concise executive memos, recommendations, policies, and implementation plans

What we’re looking for

Ideally, you have significant professional experience in one or more of the following:

— Corporate / commercial law
— Healthcare regulatory matters
— Technology or SaaS legal work
— Privacy and data protection
— Regulatory compliance
— Enterprise GRC / risk management
— AML/KYC and financial crime compliance
— AI governance
— Corporate governance and transactions

Experience working with large healthcare organizations, technology companies, regulated businesses, or enterprise clients is a plus.

Engagement

Remote, freelance/contract basis. Projects can range from short advisory assignments to ongoing support depending on the consultant’s expertise and availability.

Please include a short overview of your background, your primary area of expertise, relevant project experience, availability, and your hourly or project-based rate.

We’ll start with a brief introductory discussion to understand your experience and determine where there may be a good fit.

We are looking for 3 female hosts/actresses for a long-term content project targeting Morocco and Algeria.

About the Project
The project is focused on trading and financial markets. You will represent the face of a TG channel and create video content based on prepared scripts provided by our team.
You do not need to be a finance or cryptocurrency expert. Your role is purely as a host/actress - presenting the prepared content naturally and confidently on camera.

Requirements
Female, preferably comfortable working on camera
Arabic-speaking :
Moroccan Arabic (Darija / Moroccan Darija)
Algerian Arabic (Algerian Darija)
Natural and engaging on-camera presence
Able to follow prepared scripts
Reliable and interested in long-term cooperation

Content Formats:
Telegram video circles
The initial volume is approximately 50 Telegram video circles.


Payment
From $500 per actress for the initial volume.
This is intended as a long-term collaboration. As the project develops and the volume of work increases, the payment rate may also be increased.


Filming
📍 Location: Remote
If necessary, we can help select and book a professional studio, and studio rental costs will be fully covered by us.
Scripts will be provided in advance, so you will have time to review and prepare for filming.

Cooperation
We work with actors on a long-term basis and conclude a cooperation agreement.
The actress is responsible only for performing the role of a host/actress and is not acting as a financial advisor or responsible for financial advice.

If you are interested, please send:
A short introduction
Your location
Your experience in presenting/acting/content creation
A few recent photos
A video sample, if available

We are looking for experienced developers to build a decentralized Token Launchpad Platform. The platform will allow Web3 projects to create and launch their own tokens, manage token sales, and provide investors with a secure and reliable way to participate in token offerings.

We are looking for developers with hands-on experience in Token Launchpad Development, Token Creation & Token Sales, Smart Contract Development, Web3 Wallet Integration, and Crypto Exchange Development.

After completing the Token Launchpad Platform, we are also planning to develop a full-fledged Crypto Exchange Platform. Therefore, we are looking for experienced developers or a team who can work with us on a long-term basis and potentially continue with the exchange development as well.

If you have relevant experience, please share your portfolio along with some previous projects you have developed in the blockchain, Web3, token launchpad, or crypto exchange space. Please also mention your specific role and contribution in those projects.

We are looking for an experienced Solana Developer to join our engineering team and help build secure, scalable, and high-performance blockchain applications on the Solana network.

You will work closely with product, frontend, backend, and blockchain engineers to design and develop decentralized applications, on-chain programs, token systems, and integrations with the Solana ecosystem.

The mission

Take Parinita Enclave and Parinita Almanac through a tightly controlled four-day launch sprint and establish a production-grade path that is technically defensible.

The four-day objective is a controlled production launch of a defined surface, not an artificial claim that every roadmap feature has reached GA. We will cut optional scope before weakening tenant isolation, durability, authorization, evidence, recoverability, or RAG grounding.

By the end of the sprint, the team must be able to show what is:

LIVE / ACCEPTED — exercised against real dependencies and cleared for the controlled launch surface.

INTEGRATION-GATED — implemented but still waiting on a real service, environment, test, benchmark, or acceptance condition.

ROADMAP / DESIGNED — intentionally not represented as production functionality.

What we are building

Parinita Enclave — Object Trust Runtime

Enclave is not intended to reinvent disk-level distributed storage. Ceph/RADOS/RGW is the Tier-0 durable object-storage substrate. Parinita's differentiation sits above it.

Stratum is the governed object transaction and trust layer. It owns the logical object lifecycle, tenant scope, object/version identity, policy envelope, Object Trust Contract, Object Passport, retention/legal-hold extensions, trust inheritance, capability leases, evidence state, and the point at which an object becomes visible as committed Enclave state.

Flash is the object-intelligence layer. It enriches objects with AI-driven classification and analysis while failing safely if AI dependencies are unavailable.

Witness establishes identity, authority, delegation, and scoped capability.

Secure evaluates whether the proposed action is permitted in the current context.

Chrysalis provides the evidence/finality integration for consequential state transitions.

The intended high-assurance object flow is conceptually:

Client → Enclave API / Stratum → Witness → Secure → Ceph durable object → Chrysalis evidence → Stratum COMMITTED/VISIBLE

If evidence or policy requirements are not satisfied, the object must not be prematurely represented as a successful high-assurance Enclave commit. The implementation must use explicit durable states and recovery semantics rather than pretending Ceph and Chrysalis share a single distributed ACID transaction.

Parinita Almanac — Sovereign, Verifiable RAG

Almanac is first and foremost a production RAG platform. It is not being repositioned away from RAG.

The core path is:

Authorized Enclave source → extract → chunk → classify → embed → hybrid retrieve → rerank → assemble grounded context → approved model generation → claim/evidence validation → answer + provenance/evidence

The 10/10 Almanac features strengthen that RAG pipeline:

Knowledge Passport — lineage for a retrieved entry/chunk back to the exact source object/version and transformation state.

Knowledge Release — a versioned corpus/index release so a consultation can identify the exact knowledge state used.

Consultation Contract — principal, purpose, corpus scope, policy, jurisdiction, model/use constraints, freshness and evidence requirements for a RAG request.

ProofRAG — material claims are mapped to authorized source evidence; insufficiently supported claims must be flagged or withheld rather than disguised by decorative citations.

Answer Passport — query fingerprint, knowledge release, retrieved evidence, ranking/reranking context, model/version, output hash, claim/evidence map, and evidence references.

Trust inheritance — applicable Enclave restrictions follow the source into chunks and derived RAG artifacts.

Contradiction handling — conflicting authoritative sources are surfaced rather than silently resolved by similarity score alone.

Knowledge recall / replay foundations — identify downstream RAG artifacts affected by a corrected or revoked source and reconstruct historical consultation state where evidence exists.

The product relationship is simple:

Enclave governs the source object and what it is allowed to become. Almanac retrieves the right authorized evidence and produces traceable RAG answers from it.

Target production architecture

Layer

Primary technology / service

Responsibility

Durable object substrate

Ceph / RADOS / RGW

S3-compatible object storage, versions, replication/EC, scrub/recovery, Object Lock where applicable

Enclave transaction plane

Stratum services + PostgreSQL

Governed object state, tenant/version identity, trust contract, passport, leases, evidence state, visibility

Object intelligence

Flash

Classification, sensitivity/secret signals, content intelligence, anomaly/ransomware signals, enrichment

Identity / authority

Witness + OIDC/JWT/JWKS

Principal identity, delegation, scoped authority, short-lived capabilities

Runtime policy

Secure

Contextual allow/deny and policy decision for protected actions

Evidence

Chrysalis

Consequential-event submission, finality state, verification reference

RAG metadata / retrieval

PostgreSQL + pgvector or approved equivalent

Corpora, entries, embeddings, full-text/vector indexes, retrieval state

Almanac RAG

Almanac / Tracker services

Ingest, chunk, embed, hybrid retrieval, rerank, context, grounded generation, ProofRAG

Model execution

Denizen Blu / approved model endpoint

Embeddings, reranking and/or generation as configured and accepted

Deployment

Kubernetes + Helm or approved target

Scheduling, rollout, secrets integration, network controls, scaling, health

Observability

Prometheus/OpenTelemetry-compatible stack or approved equivalent

Metrics, traces, logs, SLO evidence, alerting

The exact production dependency endpoints and credentials must be supplied and validated in the deployment environment. The team must not substitute local mocks and then label the result “production.”

Open roles

We expect to engage multiple people. Senior, Staff and Principal-level candidates are welcome across the roles below. Strong engineers can own more than one workstream, but nobody is expected to be expert in every layer.

1. Technical Launch Lead / Staff-Principal Distributed Systems Engineer

Mission

Own the end-to-end launch architecture and force clarity at every boundary between storage, object state, identity, policy, evidence, RAG and operations.

Responsibilities

Audit the current Enclave and Almanac repositories, deployment manifests, database migrations, tests and runbooks.

Convert ambiguous cross-service behavior into explicit contracts, state machines and failure semantics.

Define the launch surface and decide what is accepted, gated or removed from scope.

Own the object state progression across Stratum, Ceph and Chrysalis without false atomicity claims.

Own service-to-service dependency contracts between Enclave, Almanac, Witness, Secure, Chrysalis and model endpoints.

Review authorization boundaries and make sure backend/internal calls cannot silently bypass the external trust model.

Establish idempotency, retry, timeout, circuit-breaker and reconciliation rules for cross-system operations.

Drive architecture decisions quickly; reject unnecessary rewrites that endanger the four-day target.

Coordinate technical owners, unblock dependencies, run daily go/no-go checkpoints and maintain the acceptance matrix.

Lead the final launch review and issue a clear GO / CONDITIONAL GO / NO-GO with evidence.

Day-4 deliverables

Approved architecture and dependency contract map.

Cross-product state/failure model.

Closed list of critical blockers for the launch surface.

Reproducible deployment path and acceptance report.

Explicit inventory of live vs integration-gated vs roadmap capabilities.

Must have

Production distributed-systems experience across multiple stateful services.

Strong PostgreSQL/data-consistency background.

Experience designing idempotent workflows and recovery after partial failure.

Ability to read Python quickly; Go or Rust experience is highly valuable.

Experience making production launch decisions under real time constraints.

2. Ceph / RGW Storage Platform Engineer

Mission

Make Tier-0 storage boring, recoverable and measurable, so Parinita engineering can concentrate on the trust and AI layers above it.

Responsibilities

Deploy or validate the target Ceph cluster and RGW topology.

Configure buckets/pools, versioning, replication or erasure coding, placement rules and Object Lock/retention capabilities where required.

Validate S3 behavior required by Enclave, including multipart, range requests, metadata, version IDs and error semantics.

Define and test the no-bypass topology: protected Enclave namespaces must not be exposed to users/services in a way that allows them to write around Stratum policy.

Validate capacity, headroom, recovery behavior, scrub/deep-scrub, rebalance behavior and expected failure domains.

Exercise disk/OSD/node failure and recovery rather than relying on documentation.

Establish metrics/alerts for cluster health, degraded PGs, recovery pressure, capacity thresholds and RGW errors/latency.

Document operational procedures for expansion, replacement, recovery and maintenance.

Work with the backend engineer to align Ceph object/version semantics with Enclave logical transaction state.

Day-4 deliverables

Working target RGW endpoint with documented storage classes/pools.

S3 contract validation for the launch surface.

No-bypass storage/network design and test evidence.

At least one tested storage failure/recovery scenario.

Ceph health/alert dashboard requirements and operator runbook.

Must have

Hands-on production Ceph/RADOS/RGW administration.

Real experience with OSD failure, PG recovery, EC/replication, scrub and cluster performance.

S3 semantics beyond simple PUT/GET demos.

Understanding of WORM/Object Lock and retention behavior.

Strong plus

Large NVMe Ceph clusters, multisite RGW, Kubernetes/Rook-Ceph, performance tuning, backup appliances or regulated storage environments.

3. Backend / Enclave Object Trust Engineer

Mission

Make Stratum the enforceable object trust boundary above Ceph.

Responsibilities

Implement/harden Stratum object APIs and durable state transitions.

Ensure object/version identity is stable and cryptographically bound to the stored content and metadata required by policy.

Implement Object Trust Contracts and Object Passports as real persisted, versioned data structures.

Implement short-lived Object Capability Leases scoped to principal, object/version, action, purpose, expiry and relevant restrictions.

Enforce retention/legal-hold behavior without depending only on application convention.

Implement evidence-gated visibility using explicit states such as PREPARED/PENDING/DURABLE/ATTESTED/COMMITTED/FAILED/QUARANTINED as appropriate.

Ensure retries cannot double-commit, lose evidence links or surface an object prematurely.

Build reconciliation workers for partial success: e.g., Ceph write succeeded but Chrysalis or metadata transition failed.

Implement trust inheritance hooks for downstream Almanac ingestion and derived artifacts.

Eliminate unsafe development fallbacks from production paths.

Write negative and concurrency tests around state transitions.

Day-4 deliverables

Tested governed PUT/GET/version flow over the real Ceph/RGW dependency.

Persisted Object Trust Contract + Object Passport lifecycle.

Evidence-gated commit/recovery behavior.

Capability-lease enforcement for at least the controlled launch surface.

Negative tests proving direct invalid transitions are rejected.

Must have

Strong backend engineering in Python, Go, Rust, Java or equivalent.

PostgreSQL transactions, locking, migrations, concurrency and idempotency.

Durable workflow/state-machine design.

Secure API design and tenant isolation.

Strong plus

S3 integrations, cryptographic metadata, policy engines, audit/evidence systems, distributed transaction patterns, event/outbox architectures.

4. RAG / Retrieval / AI Engineer — Almanac

Mission

Ship a production RAG path that is retrieval-first, evidence-aware and precise about what it knows.

Responsibilities

Harden source ingestion from authorized Enclave objects.

Implement reliable extraction for the accepted launch document types and record parser/version metadata.

Design chunking appropriate to source type and preserve exact source coordinates needed for citations.

Build and validate embedding generation, version pinning and index compatibility.

Operate PostgreSQL/pgvector or the accepted retrieval backend with tenant/corpus isolation.

Implement hybrid retrieval (vector + lexical/filtering), candidate generation, reranking and deterministic evidence packaging.

Create/version Knowledge Passports and Knowledge Releases.

Implement Consultation Contracts that constrain corpus, purpose, principal, policy, model, freshness and evidence requirements.

Harden prompt-injection/content-poisoning handling so retrieved document text is treated as untrusted evidence, not executable instruction.

Implement ProofRAG at the claim/evidence level, not merely by checking whether the LLM emitted [1] or [E3] tokens.

Require abstention/insufficient-evidence behavior when material claims are unsupported.

Surface contradictory source evidence where confidence/authority cannot safely resolve it.

Generate Answer Passports linking the answer to source versions, retrieval state, model/version, claim/evidence map and evidence references.

Build evaluation cases for retrieval quality, citation precision, answer grounding, contradiction handling and negative authorization.

Day-4 deliverables

Working Enclave-source-to-RAG-answer flow against real dependencies.

Versioned source/chunk/embedding/retrieval lineage for the launch corpus.

Hybrid retrieval + reranking evaluation report.

Claim-level citation/grounding tests with abstention cases.

Answer Passport for every accepted controlled-launch RAG answer.

Must have

Production RAG experience beyond prompt demos.

Embeddings, vector search, lexical retrieval and rerankers.

pgvector, Elasticsearch/OpenSearch, Vespa, Qdrant, Milvus or equivalent hands-on experience.

Document ingestion/extraction and chunking trade-offs.

RAG evaluation: recall/precision, ranking quality, citation quality, answer grounding and failure analysis.

Strong plus

Enterprise/regulated RAG, provenance, temporal/versioned retrieval, multimodal retrieval, knowledge graphs, secure RAG, red-team testing for prompt injection.

5. Security / Identity / Policy Engineer

Mission

Ensure every protected action has a real identity, scoped authority and deny-by-default policy path.

Responsibilities

Integrate/validate OIDC/JWT/JWKS authentication in production mode.

Integrate Witness authority/delegation decisions for customer, agent and service principals.

Integrate Secure runtime policy checks for protected operations.

Define service identities and least-privilege permissions across Enclave, Almanac, Ceph/RGW, PostgreSQL, Chrysalis and model endpoints.

Remove development tenant-header/default-token behavior from the production path.

Design capability-lease verification and anti-replay/expiry behavior.

Validate secrets handling and KMS/HSM integration contracts; do not embed long-lived secrets in images/config maps.

Establish mTLS/service-authentication requirements where appropriate.

Lock down network egress/ingress so “sovereign” does not mean a NetworkPolicy that still permits unrestricted outbound traffic.

Build negative tests for cross-tenant access, privilege escalation, invalid delegation, expired capability, bad issuer/audience, policy-denied operations and internal-service bypass.

Review audit logs to ensure sensitive payloads/secrets are not leaked.

Day-4 deliverables

Production auth path exercised with the real identity endpoint or explicitly gated if unavailable.

Witness/Secure decision matrix for launch operations.

Service-to-service identity map and secrets plan.

Negative-security test results.

Network/egress policy appropriate to the launch environment.

Must have

OIDC/OAuth2/JWT/JWKS and service identity.

RBAC/ABAC/capability/delegation patterns.

API and microservice threat modeling.

Secrets/key management; KMS/HSM integration patterns.

Network segmentation and deny-by-default controls.

6. Platform / SRE / Kubernetes Engineer

Mission

Turn the code into a repeatable, observable, recoverable production service.

Responsibilities

Harden Docker images and Helm/Kubernetes manifests or the approved deployment target.

Implement production configuration validation and fail-closed startup for required dependencies.

Manage PostgreSQL/pgvector deployment assumptions, migrations and upgrade/rollback safety.

Configure readiness/liveness/startup probes that reflect real dependency state without causing restart storms.

Define resource requests/limits, autoscaling, disruption budgets and rollout policy.

Implement secrets integration and immutable image/version promotion.

Establish CI/CD checks: lint, tests, dependency/security scan, migration check, image scan and deploy validation.

Instrument metrics, traces and structured logs for Enclave and Almanac critical paths.

Build dashboards/alerts for object state backlog, failed evidence submissions, Flash/AI queue health, ingestion failures, index freshness, RAG latency, retrieval quality signals and dependency health.

Execute backup/restore for PostgreSQL state and document Ceph recovery dependencies.

Exercise rollout, rollback and restore before customer exposure.

Create a launch-day runbook and incident escalation path.

Day-4 deliverables

One-command or documented reproducible deployment from approved prerequisites.

Immutable image/version manifest.

Monitoring/alerting baseline.

Exercised DB backup/restore and application rollback.

Production runbook with dependency failure actions.

Must have

Kubernetes/Helm or equivalent production operations.

Stateful workloads and PostgreSQL operations.

CI/CD, containers, secret management and observability.

Real incident/recovery experience.

7. QA / Performance / Resilience Engineer

Mission

Prove the launch surface by trying to break it.

Responsibilities

Build a cross-product acceptance matrix covering functionality, isolation, security, recovery, performance and evidence.

Create deterministic integration fixtures for Enclave + Almanac.

Test cross-tenant/cross-corpus denial paths.

Exercise retries, duplicate requests, stale tokens, expired leases and partial dependency failures.

Test service restart during object commit, evidence submission, ingestion and RAG consultation.

Validate no object becomes visible before its required Enclave commit state.

Validate no Almanac answer can retrieve from an unauthorized corpus.

Validate ProofRAG behavior on supported claims, unsupported claims, conflicting sources and malicious prompt-injection content.

Establish baseline throughput/latency for the launch surface and record the test method rather than publishing unmeasured SLA claims.

Exercise Ceph failure/recovery with the storage engineer and DB restore/rollback with SRE.

Produce a final release-evidence pack with test inputs, results, failures, residual risks and rerun instructions.

Day-4 deliverables

Release acceptance matrix with PASS/FAIL/GATED status.

Functional + negative-security + tenant-isolation suite.

Dependency-outage/restart/recovery evidence.

Initial performance baseline with methodology.

Final critical/high defect list and retest status.

Must have

Production integration/acceptance testing across distributed services.

Negative security and tenant-isolation testing.

Load/performance testing with reproducible methodology.

Failure injection and recovery validation.

8. Optional: AI/RAG Evaluation & Red-Team Specialist

We may also engage a dedicated evaluator if the RAG engineer should remain focused on implementation.

Focus

Build a gold evaluation set for retrieval and grounded answer quality.

Measure retrieval recall, ranking quality, source attribution, unsupported-claim rate and abstention quality.

Adversarially test indirect prompt injection, conflicting documents, stale/superseded content and poisoned sources.

Review Answer Passports and claim/evidence maps for false confidence.

Define regression gates for model, embedding, reranker and chunking changes.

Day 0 — prerequisites before the four-day clock starts

The sprint is only meaningful if the team has access to real dependencies. Before Day 1, Parinita and the selected team should confirm availability of:

Current Enclave and Almanac repositories and issue/acceptance lists.

Target deployment environment and sufficient cluster privileges.

Ceph/RGW endpoint and administrative contact/credentials required for setup.

PostgreSQL/pgvector or authority to deploy it.

OIDC/JWKS issuer and test principals.

Witness, Secure and Chrysalis integration endpoints or a written statement that a specific dependency remains gated.

Approved model/embedding/reranking endpoints for Almanac.

Required DNS/TLS/secrets/KMS/HSM integration details for the launch environment.

A representative but safe test corpus and tenant matrix.

Named Parinita decision-maker for rapid architecture/scope decisions.

A missing external dependency does not justify a fake local substitute being called production. It becomes an explicit integration gate.

Four-day execution plan

Day 1 — Establish truth, deploy foundations, freeze contracts

Morning

Repository and deployment audit.

Re-run existing tests and classify what they actually prove.

Identify critical defects and stale/hallucinated assumptions.

Freeze launch scope and assign workstream owners.

Validate Ceph, DB, identity, policy, evidence and model endpoints.

Afternoon

Deploy/validate Ceph RGW + PostgreSQL/pgvector + application namespaces.

Apply DB migrations and seed controlled test tenants.

Establish service identities/secrets/network boundaries.

Define Stratum object-state and Almanac consultation-state contracts.

End-of-day exit criteria

All required dependencies are either reachable and tested or explicitly GATED.

Critical architecture decisions are closed.

The team can deploy all in-scope services in the target environment.

No one is still assuming a mock/local service is equivalent to the production dependency.

Day 2 — Enclave governed object lifecycle

Morning

Prove governed PUT/GET/version/list flow through Stratum over Ceph.

Persist object/version identity, hash, trust contract and passport.

Validate tenant boundaries, retention/legal hold and no-bypass topology.

Afternoon

Integrate Witness/Secure on protected actions.

Exercise Chrysalis submission/finality states for evidence-gated operations.

Validate partial-failure reconciliation and idempotent retry.

Validate Flash enrichment state and safe failure behavior.

End-of-day exit criteria

A controlled launch tenant can write/read a governed object.

Direct policy bypass is demonstrably blocked for the protected namespace.

Object state survives process restart and dependency failure.

A failed evidence/AI dependency does not silently produce a false successful state.

Day 3 — Almanac source-to-answer RAG lineage

Morning

Ingest authorized Enclave objects.

Extract/chunk supported documents with exact source coordinates.

Generate embeddings with pinned model/version and build a Knowledge Release.

Validate tenant/corpus isolation and retrieval filters.

Afternoon

Exercise hybrid retrieval + reranking against a representative evaluation set.

Apply Consultation Contracts before retrieval/generation.

Generate grounded answers through the approved model endpoint.

Enforce claim/evidence mapping and abstention.

Produce Answer Passports tied to exact object versions and Knowledge Release.

End-of-day exit criteria

The team can trace an accepted answer from claim → retrieved passage → chunk → source object/version.

Unauthorized corpus retrieval fails.

Unsupported questions demonstrate safe insufficient-evidence behavior.

Prompt-injection content is treated as untrusted evidence rather than higher-priority instruction.

Day 4 — Break it, recover it, measure it, launch only what passes

Morning

Cross-tenant negative tests.

Kill/restart critical services during object write and RAG consultation.

Simulate identity/policy/evidence/model dependency outage.

Exercise DB backup/restore and application rollback.

Run controlled load/performance baseline.

Afternoon

Close critical/high launch blockers or remove affected surface from launch.

Run final acceptance suite.

Review security, data isolation, recovery and observability evidence.

Publish live/gated/roadmap matrix.

Issue GO / CONDITIONAL GO / NO-GO.

Launch rule: no deadline overrides a failed trust, tenant-isolation, durability, authorization, evidence or grounded-RAG gate.

Non-negotiable acceptance requirements

Enclave

Protected writes go through the governed Stratum path.

Production tenant identity is not taken from a caller-controlled development header.

Object Trust Contract and Object Passport are durable and tied to the exact object version.

Required evidence state is distinguishable as submitted/finalized/failed; an arbitrary ID is not assumed to prove finality.

Partial failure is recoverable and idempotent.

Retention/legal hold behavior is negative-tested.

Flash failure is visible and does not silently fabricate semantic output.

Ceph degradation/recovery behavior is understood and observable.

Almanac RAG

Authorization and corpus scoping happen before retrieval.

Exact source object/version lineage survives extraction, chunking and indexing.

Embedding/rerank/generation model/version are recorded where needed for reproducibility/audit.

Retrieval uses the accepted combination of vector, lexical and structured filtering appropriate to the launch corpus.

Material claims have source evidence or are explicitly unsupported/abstained.

Contradictory sources are not silently disguised as a single fact where the system lacks authority to resolve them.

Answer Passport records the accepted consultation lineage.

An LLM's own “evidence analysis” is never treated as independent proof that the answer is true.

Platform / security

No default secrets, dev auth, mock tenants or permissive production fallback.

Egress/ingress rules are explicit and testable.

Backups restore; rollbacks work.

Dashboards/alerts expose queues, dependency failures and degraded states.

The exact deployed image/build can be identified.

Production claims are tied to acceptance evidence, not architecture diagrams.

Engineering rules for this sprint

1. Do not rewrite Ceph. Use the mature storage substrate unless a specific launch-blocking defect proves otherwise.

2. Do not hide partial failure. Persist explicit state and reconcile it.

3. Do not call local mocks “production integrations.” Mark the dependency gated.

4. Do not make RAG look grounded by decorating answers with citations. Prove claim-to-source mapping for the accepted surface.

5. Do not let AI-generated analysis become the root of trust. Cryptographic evidence can prove what happened, not whether an LLM's reasoning was correct.

6. Do not publish unmeasured performance/SLA claims. Record methodology, then publish accepted measurements.

7. Do not bypass policy for internal services. Service-to-service authority is still authority.

8. Do not trade isolation, durability or recoverability for the four-day deadline. Reduce scope instead.

What strong candidates look like

You have personally operated systems where failure mattered. You can describe what broke, how you found it, what state was left behind, how you recovered it, and how you prevented recurrence.

We value engineers who are comfortable saying “this is implemented but not yet production-accepted” rather than turning roadmap intent into claims.

Strong candidates typically have several of the following:

Stateful distributed systems under real load.

Ceph/RADOS/RGW, object storage, S3 or storage control planes.

PostgreSQL transactions/migrations/HA and pgvector or comparable retrieval systems.

Production RAG with measurable retrieval and grounding evaluation.

OIDC/JWT/JWKS, policy engines, capability/delegation systems.

Kubernetes/Helm and production SRE.

Evidence/provenance/audit pipelines.

Cryptographic service integrations, KMS/HSM or signing systems.

Multi-tenant security architecture.

Incident response and disaster recovery.

Current services are heavily Python-oriented. Strong Go or Rust experience is valuable, particularly for systems/performance work.

Who should not apply

This role is not a fit if your relevant experience is primarily:

Building chatbot demos around managed APIs.

Running local Docker Compose and calling it production.

Writing architecture documents without owning deployment/failure behavior.

Assuming Kubernetes automatically solves security/reliability.

Treating a vector database as a complete RAG system.

Recommending a new framework/database/storage engine before understanding the existing code.

Avoiding operational responsibility after merge.

Selection process

We want a fast, high-signal process because the work is immediate.

Step 1 — written response. Answer the role-specific questions below and include links or concise descriptions of relevant production work.

Step 2 — technical discussion. 30–45 minutes focused on one real system you owned and one failure scenario relevant to your workstream.

Step 3 — repo/architecture fit. Selected candidates review the launch brief/repository and identify the first changes they would make. We are evaluating judgment, not presentation theater.

Step 4 — engagement and sprint start. Confirm scope, rate/commercial terms, availability, owner and Day-1 deliverables.

Application questions

Answer the general questions plus those relevant to your role.

General

1. Which role(s) are you applying for? State Senior / Staff / Principal level if useful, but emphasize what you can personally own.

2. What can you commit to delivering in the next four days?

3. Describe one production system you personally built or operated that is directly relevant. What failed in production and what did you do?

4. What timezone are you in, what hours can you overlap, and when can you start?

5. Do you prefer hourly, daily or fixed-scope commercial terms? Provide your rate/proposal.

6. Are you applying individually or as part of a team? If a team, list each person, role and concrete deliverable.

Storage / Ceph

7. Describe a real Ceph/RGW incident you handled: what failed, what did cluster state look like, how did you recover it, and what did you change afterward?

8. How would you prevent users and internal services from bypassing Stratum while still allowing Stratum/RGW to scale?

9. For a high-assurance bucket, how would you combine Ceph Object Lock/retention with an application-level governed state machine without creating contradictory sources of truth?

Backend / distributed systems

10. Design an evidence-gated Enclave PUT where Ceph can succeed and Chrysalis can time out. What durable states, idempotency keys, retry rules and reconciliation jobs do you use?

11. How do you prevent a retry from producing two logical Enclave versions or exposing a PENDING object as COMMITTED?

12. What belongs in the Object Trust Contract vs the Object Passport vs operational metadata?

RAG / retrieval / AI

13. How would you evaluate whether hybrid retrieval + reranking actually improved Almanac instead of merely changing scores?

14. How would you enforce claim-level evidence and abstention rather than checking that an answer contains citation markers?

15. How would you represent versioned corpus/index state so a historical Answer Passport can identify what was searchable at consultation time?

16. How would you handle two authoritative source documents that materially contradict each other?

17. Describe your defense against indirect prompt injection contained inside retrieved enterprise documents.

Security / policy

18. How would you model authority for a human, an AI agent acting under delegation, and an internal service without giving any of them blanket storage credentials?

19. What claims must you validate in JWT/OIDC tokens and how do you handle key rotation, issuer/audience errors and clock skew?

20. What would you test to prove service-to-service policy cannot be bypassed through an alternate internal endpoint?

Platform / SRE

21. What must pass before you permit production traffic to a new Enclave/Almanac release?

22. How would you deploy DB migrations safely with multiple application replicas and a required rollback path?

23. What are the first ten metrics/alerts you would require across Ceph, Stratum, Flash and Almanac?

24. Describe a backup/restore or disaster-recovery test you personally executed rather than merely documented.

QA / resilience

25. List the first ten failure/negative tests you would run against Enclave + Almanac together.

26. How would you demonstrate that a tenant can never retrieve another tenant's object or RAG chunk, including through caches/indexes?

27. How would you build a repeatable performance baseline without turning a four-day benchmark into an unsupported SLA promise?

What the team receives

Selected candidates will receive the current code repositories, architecture/white-paper packet, build/operate material, hallucination/overclaim audit, acceptance requirements, and the credentials/environment information Parinita is able to provide for the launch sprint.

You are expected to challenge contradictions in those materials. The code, the deployed environment and repeatable tests determine technical truth.


Detailed Recruiting Brief v3 | September 2026 | Page

PARINITA AI EDGE | ENCLAVE + ALMANAC ENGINEERING LAUNCH TEAM

ENGAGEMENT • IMMEDIATE START

Build the trusted data + RAG path with us.

Four-day controlled-launch sprint first. Ongoing production engineering and operations work available for strong performers and teams.

Apply for the workstream you can own. We are willing to hire multiple specialists rather than force one person to cover every domain.

ENCLAVE

Make object trust enforceable.

ALMANAC

Make RAG evidence precise.

PRODUCTION

Make failure recoverable.

What to send in your first response

The role(s) or workstream(s) you want to own.

One directly relevant production system you personally built or operated, including a failure you handled.

Your earliest start, timezone and realistic availability across the four-day sprint.

Your hourly, daily or fixed-scope commercial proposal.

Answers to the role-specific technical questions in this brief; if applying as a team, map each person to a concrete deliverable.

If you can make storage boring, object trust enforceable, authorization fail closed, RAG evidence precise, and production failures recoverable, we want to hear from you.

We are looking for an experienced Video Editor to create elevated, engaging social media recap videos from industry panel discussions for Luna PR, a global PR and communications agency working across technology, finance, crypto, AI and robotics.

This role goes beyond simply cutting footage. We are looking for someone with strong editorial judgment who can understand a panel conversation, identify the most interesting and relevant moments, and turn them into concise, impactful social content.

What you’ll be responsible for:
- Reviewing full panel discussions and identifying the strongest moments, quotes and insights
- Editing these into dynamic, polished social media recap videos
- Creating concise on-screen copy, hooks and supporting text where needed
- Adding accurate, well-designed subtitles
- Understanding which statements or moments deserve emphasis
- Creating a strong narrative and pacing rather than simply compiling highlights
- Selecting relevant B-roll, graphics or supporting visual elements when appropriate
- Maintaining an elevated, contemporary visual style suitable for a global PR and communications company

What we’re looking for:
- Strong video editing and storytelling skills
- Experience creating short-form social content from interviews, podcasts, conferences or panel discussions
- Good English and confidence working with spoken content
- Good copywriting instincts
- General understanding of technology, finance, crypto, AI and/or robotics — you don't need to be an expert, but you should be comfortable understanding industry conversations
- Ability to work independently and make editorial decisions
- Strong attention to detail and a polished visual sensibility

You will work closely with our Head of Content Creation, who will provide the brief, creative direction and feedback and coordinate the project with you.

We would like to begin with one panel recap video as a paid trial project. If the collaboration is successful and the quality matches what we are looking for, we are interested in establishing an ongoing relationship and becoming a regular client.
When applying, please share relevant examples of panel, interview, podcast, event or thought-leadership content you have edited. We are particularly interested in seeing work where you transformed longer-form conversations into compelling short-form social content.

Studio36 is a creative studio operating at the intersection of Web3, crypto, and emerging technologies. We work with innovative companies across blockchain, fintech, and technology sectors, creating high-quality visual identities, campaigns, and digital assets.
We are currently looking for a freelance graphic designer to support our team on a project basis, with the potential to develop into a long-term collaboration.
This role is execution-focused. The creative direction, concepts, and brand systems will be provided by our internal team. We are looking for someone who can translate direction into precise, polished, and production-ready visual assets.
Responsibilities:
- Execute visual designs based on provided creative direction and brand guidelines
- Create digital assets such as social media graphics, presentation slides, marketing materials, and brand assets
- Ensure high attention to detail, alignment, spacing, typography, and overall visual quality
- Prepare final files in professional, production-ready formats
- Collaborate with our team to ensure consistency across deliverables

Requirements:
- Strong graphic design skills
- Ability to follow creative direction accurately and execute at a high level
- Proficiency in Figma and Adobe Creative Suite (Photoshop, Illustrator, InDesign) and usage of AI tools.
- Strong typography, composition, and layout skills
- Reliable, responsive, and professional communication
- Experience in Web3, crypto, tech, or fintech is an advantage

Engagement Details:
- Hourly-based freelance role
- Initial engagement will be project-based
- Opportunity for ongoing, long-term collaboration depending on performance and studio needs
- Flexible, remote work

Studio36 operates at a high creative standard and values designers who are detail-oriented, precise, and committed to quality.
Please include your portfolio with relevant work when applying.

We’re looking for a Senior DeFi Developer to join our engineering team and help design, build, and scale next-generation decentralized financial products.

You’ll work across smart contracts, blockchain infrastructure, and backend systems, taking ownership of critical components from architecture and development through testing, deployment, and optimization.

This role is ideal for an experienced blockchain engineer who understands not only how to write smart contracts, but also the economic, security, and technical considerations behind DeFi protocols.