Skip to content

Smart contracts and NFTs: understanding and framing a project

Project teams, innovation teams, schools and business departments · 2 days (14 hours) · in-house, on site or remote · 12 participants maximum

At a glance

Duration
2 jours (14 heures)
Format
On site and remote
Group size
12 participants maximum
Level
Beginner
Audience
Project teams and project managers who receive a blockchain request without knowing how to assess it
Prerequisites
No technical prerequisite: we read smart contracts, we do not write them.
Methods
Short talks, twenty minutes at most, followed by a workshop on a public explorer or on a request brought by participants
Assessment
Beforehand: a positioning questionnaire (blockchain requests received, level of familiarity, expectations), which adjusts the examples
Lead time
Scheduled during framing, to suit your availability
Pricing
On a quote basis, depending on format, duration and number of participants. The first call is free.
Accessibility and disability
See the dedicated section

A blockchain request rarely comes through the technical door. It comes from a partner offering NFTs, a director who read an article, a customer who wants “traceability”, and nobody on the project team is in a position to say whether it is a good idea. That is what these two days are for: understanding what a blockchain actually does, and above all what it does not; reading a smart contract without knowing how to code, enough to ask the right questions of the people who build it; seeing what an NFT can represent beyond images (titles, tickets, traceability); measuring the real risks (keys, oracles, gas costs, regulatory framework); and framing a request with written go / no-go criteria, including what running a node really costs. The programme was delivered over two days at the FIB in Barcelona. It contains no investment advice and gives no opinion on any asset: it is about projects, not prices.

Learning objectives

  • Explain in five minutes, without jargon, what a blockchain brings (shared ledger, tamper resistance, no intermediary) and what it does not
  • Recognise the requests an ordinary database handles better, and say so with arguments
  • Read the structure of a smart contract (state, functions, events, admin rights) and ask the questions that matter of the team building it
  • Describe what an NFT technically represents, and assess a non-image use case: title, ticket, attestation, traceability
  • Identify the risks of a blockchain project: key management, dependence on oracles, gas costs, irreversibility, regulatory framework to have qualified
  • Frame a blockchain request with a list of questions and written go / no-go criteria before any decision
  • Estimate the running costs of a node or of network access, and compare them with access through a provider
  • Write a one-page framing note that recommends going ahead, reformulating or declining

Programme

01What a blockchain is, and what it is not

2 h 30
  • A shared, replicated ledger whose history cannot be rewritten: what that allows, and the price it costs in performance and flexibility
  • Public, permissioned, private blockchains: three different objects, three reasons to exist
  • Transaction, block, consensus, fees: the minimum vocabulary, explained live on a public explorer
  • Keys, addresses and wallets: who holds what, and what happens when a key is lost
  • When not to use it at all: the six situations where a database, an electronic signature or a simple timestamp do better and cheaper
  • Workshop: each participant restates a blockchain request heard in their organisation, and the group classifies it

02Reading a smart contract without coding

2 h 30
  • What a smart contract is: a programme that runs on the network, not a contract in the legal sense
  • The structure to spot: stored state, public functions, emitted events, admin rights
  • The questions that matter: who can pause the contract, who can upgrade it, who can withdraw the funds, and has the code been reviewed by a third party
  • Reading a deployed contract on a public explorer: verified code, transactions, holders
  • Why “code is law” is a phrase to handle with care
  • Workshop: guided reading of two public contracts, then a list of questions to ask a development team

03NFTs beyond images

2 hours
  • What an NFT technically represents: a unique identifier, an owner address, a link to metadata
  • Where the image or document really lives: on chain, off chain, and what that changes for durability
  • Use cases beyond speculation: titles and attestations, ticketing, batch traceability, access rights
  • What an NFT does not prove: the authenticity of the physical object, the identity of the holder, the value
  • Workshop: assessing three NFT use cases proposed by the group on a usefulness / alternative / cost grid

04Risks: keys, oracles, gas, regulation

2 h 30
  • Key management: who holds the keys of a company contract, how they are protected, what happens when they are lost
  • Oracles: a smart contract cannot see the outside world, and whoever tells it the truth becomes the point of trust
  • Gas costs: why an operation can cost ten times more from one day to the next, and how to cap it
  • Irreversibility: no rollback, no customer support, no undo button
  • Regulatory framework: the questions to have qualified by a lawyer (nature of the tokens, identification obligations, tax treatment), without answering them yourself
  • What went wrong in public projects, without naming any project and without invented cases: the three most frequent incident patterns

05Running a node: what it really costs

2 hours
  • Full node, light node, validator, access through a provider: four levels of involvement, four levels of cost
  • What it takes to run a node: machine, storage, bandwidth, updates, monitoring, on-call
  • Why direct network access drops without warning, and what an intermediate layer (cache, rate limiting, health check) brings
  • Build or buy: the decision grid between a node run in-house and an access provider
  • Workshop: estimating the order of magnitude of running costs for the case brought in, in days and in infrastructure

06Framing a project: questions, go / no-go criteria, framing note

2 h 30
  • The list of questions to ask before accepting a blockchain request: real problem, conventional alternative, who writes, who reads, who pays
  • Written go / no-go criteria: need for a shared ledger between parties that do not trust each other, no cheaper alternative, ability to manage keys, regulatory framework qualified
  • The three outcomes of a framing: go ahead, reformulate without blockchain, decline
  • Workshop: each sub-group writes the one-page framing note for a request brought in, and presents it
  • Validation quiz, individual action plan and handover of the take-away materials

Who it is for

  • Project teams and project managers who receive a blockchain request without knowing how to assess it
  • Innovation teams and business departments tasked with examining an NFT or traceability topic
  • IT and management schools wanting a two-day module with no coding prerequisite
  • IT leads asked for a technical opinion on a Web3 partnership
  • Lawyers and compliance officers who want to understand how it works before qualifying it

What you take away

  • The list of six situations where not to use a blockchain, with the alternative for each
  • The smart contract reading grid: structure to spot and questions to ask the development team
  • The NFT use case assessment grid: usefulness, alternative, cost
  • The list of risks to examine (keys, oracles, gas, irreversibility, regulation) and who to have them qualified by
  • A build-or-buy decision grid for network access, with the cost items of a node
  • The one-page framing note template with go / no-go criteria, and the one written in session
  • The full session materials

Prerequisites

  • No technical prerequisite: we read smart contracts, we do not write them.
  • No prior knowledge of blockchain or cryptocurrencies is needed.
  • Having a workstation with a browser: the reading workshops use public blockchain explorers.
  • Bringing, if one exists, a real current or past blockchain request from the company: it is the material for the framing in the last module.

Teaching methods

  • Short talks, twenty minutes at most, followed by a workshop on a public explorer or on a request brought by participants
  • Reading contracts actually deployed, live, rather than diagrams
  • Not a line of code written over the two days: we read, we question, we frame
  • Decision grids filled in during the session: usefulness / alternative / cost for NFTs, go / no-go for the framing
  • Feedback from the real operation of a validator and of a containerised RPC access: what drops, what it costs, what gets monitored
  • Sub-groups of three to four participants for the final framing, with cross-presentation
  • No demonstration of buying, selling or holding: cryptocurrencies are covered as a fee mechanism, never as an asset to acquire

Assessment of learning

  • Beforehand: a positioning questionnaire (blockchain requests received, level of familiarity, expectations), which adjusts the examples
  • During the session: request classification exercise (module 1) and question list produced after reading contracts (module 2), corrected in session
  • During the session: NFT use case assessment grid (module 3) reviewed on three criteria: usefulness demonstrated, alternative examined, cost estimated
  • At the end: a one-page framing note presented by each sub-group, assessed on the consistency between questions asked, go / no-go criteria and recommendation
  • At the end: a validation quiz covering the six modules, corrected and discussed in the room
  • Four to six weeks later: a one-hour remote follow-up on the blockchain requests handled since the session and on the framing actually applied

Where what I teach comes from

Adrien Bouthet, freelance IT Project Manager and Product Owner based in Bordeaux, with eight years of experience steering digital projects. I have been working with blockchain since 2019, not as a watching brief but as infrastructure: smart contracts written and deployed, a validator in operation, then the industrialisation of a containerised RPC access with caching, rate limiting and health checks, because direct network access drops without warning. That is where the module on the running costs of a node and the risks section come from: what drops, what costs, what gets monitored, I went through it before teaching it. Those are results from assignments and from my own projects, not a promise made to participants. I delivered this programme over two days at the FIB in Barcelona, and I have been a trainer in programming and management with schools since 2020. Two points that matter: I give no investment advice and no opinion on any asset; and the regulatory framework is treated as a list of questions for a lawyer to qualify, never as an answer.

Real example

The module on the running costs of a node comes from my own ground. I have been working with blockchain since 2019, I have operated a validator and I have industrialised, for a product I build myself, a containerised RPC access with caching, rate limiting and health checks. A project result, not a promise made to participants: it is what the build-or-buy grid worked on in session rests on.

Read the case study

Frequently asked questions

Does this training give an opinion on cryptocurrencies or on an asset?+

No, and it is a rule of the session. No investment advice, no opinion on a token, a project or a price. Cryptocurrencies are covered only as the fee and operating mechanism of the network. If the question is “should I buy”, the answer is that it is not the subject, and that it belongs to an authorised adviser, not to a trainer.

Do participants need to code?+

No. We read smart contracts deployed on public explorers, spot their structure and draw questions from them; nobody writes code during the two days. Developers who attend mostly get the framing and risk parts, which are not learnt from documentation.

Is this a training for launching an NFT project?+

It is a training for deciding whether to launch it. Some framings end with “reformulate without blockchain” or “decline”, and that is as useful an outcome as a go. If the decision is to go ahead, the framing note written in session is the starting point of the project.

Is the regulatory framework covered?+

It is identified, not settled. The risks module lists the questions for a lawyer to qualify: nature of the tokens, user identification obligations, tax treatment. I am neither a lawyer nor a legal adviser, and the session gives no legal advice.

On site or remote?+

Both. On site at your premises or your school, in Bordeaux and across Nouvelle-Aquitaine; remotely anywhere in France. The reading workshops use public explorers reachable from any browser, which makes the remote format as effective as the classroom.

How many participants at most?+

Twelve. The final framing is done in sub-groups of three to four, with cross-presentation; beyond twelve, the presentations no longer fit in the last module. In a school, a larger cohort is split into several sessions.

How is this different from a blockchain consulting assignment?+

The training makes your team able to frame a request on its own; on an assignment, I am the one examining feasibility, architecture or the industrialisation of network access. The two combine: train the team first, then step in on the project it has decided to launch.

Framework and terms

Funding

These sessions are invoiced directly to the company, out of its own skills development budget. They are not eligible for pooled funding schemes (OPCO, CPF, France Travail), which require Qualiopi certification.

Certification

This session is not a certifying course. I do not deliver any Scrum.org, Scrum Alliance, Scaled Agile (SAFe) or PeopleCert (ITIL) certification, nor any qualification registered with the RNCP or the Répertoire spécifique. The goal is operational: practices you can apply, not a diploma.

Contractual framework

Each session is covered by a professional training agreement (convention de formation professionnelle) signed before the start, setting out the objectives, the programme, the duration, the delivery arrangements and the agreed fee. The internal rules applicable to the session are handed to participants at the opening.

Certificate of attendance

A certificate of completion is handed to each participant at the end of the session. It states the objectives, the nature and the duration of the training, along with the results of the assessment of learning.

Accessibility and disability

Disability referent: Adrien Bouthet, contact@adrienbouthet.fr. Any situation requiring an adjustment (access to the premises, adaptation of the materials, of the pace or of the assessment arrangements) is examined during the framing phase, within 5 working days. If the adjustment exceeds our means, we refer to specialised resources (Agefiph, Cap emploi).

A blockchain request to frame

Book a free first call. We look at the request coming your way, the profile of the participants and the format, in a company or in a school, and I tell you straight whether these two days are the right starting point.

The matching service

Blockchain and Web3 consulting