ETF Bitcoin Spot ou Futures : quelles différences pour l'investisseur ?

·6 views

Les ETF Bitcoin Spot et Futures sont deux fonds cotés en bourse donnant accès au Bitcoin, mais selon des mécanismes différents. L'ETF Spot détient directement les bitcoins et suit de près le cours réel de l'actif, tandis que l'ETF Futures s'appuie sur des contrats à terme qui fixent un prix pour une livraison future. Le second est influencé par les primes ou décotes de ces contrats, ce qui peut créer un écart avec le spot. Les frais et la liquidité diffèrent également : l'ETF Spot est généralement moins coûteux et plus liquide, alors que l'ETF Futures peut supporter des frais de financement. Le choix dépend donc de la recherche d'une exposition simple et directe ou d'une stratégie plus complexe liée aux contrats à terme.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

How to Set Google Preferred Sources to Shape AI Answers and News Results

Google's October 15 update lets users choose preferred publishers that appear higher in AI Mode and AI Overviews answers. Preferred sources also gain prominence in the News carousel within AI Mode, according to the company. Google reports that usage of the feature has grown sevenfold as people curate their results. Users can set their sources by searching a topic, opening the customize icon beside Top stories, and adding trusted publications, then refreshing results. The guide argues that choosing outlets you actually read yields more in-depth answers.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Pujo Atlas: Open Map Helps Plan Durga Puja Pandal Visits in Kolkata

Pujo Atlas is a free, browser-based map and itinerary planner for finding Durga Puja pandals in Kolkata and across West Bengal. It combines a Kolkata puja guide with a government puja directory, allowing users to search by pandal, locality, coordinates, or DIGIPIN. Users can browse nearby results on a clustered map and save pandals to a hopping list to plan their route. The project currently has no paying users or revenue, and its creator has stated it does not yet use open-source AI despite being submitted to a related challenge.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

What a pentest closure record should contain for auditors and customers

A pentest report lists vulnerabilities, but auditors and enterprise customers want a record showing what was fixed, what changed, and proof the fix worked. The article proposes six fields per finding: a stable ID and weakness with location, scope agreement, the change and its rationale, who authored and reviewed it, a rescan confirming the fix, and the merge date. It illustrates this with a rehearsal Fix Sprint on the deliberately vulnerable OWASP NodeGoat app, where 15 of 16 in-scope findings were fixed across five pull requests. One finding, a committed TLS private key, was explained rather than changed, since deleting the file would not remove it from git history. The article also warns against closing findings by deleting evidence, merging without rescanning, and bundling many fixes into one pull request.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Remote NT Housing Repair Triage System Ranks Fault Urgency, Not Tenant Identity

A student team built ReachNT, a prototype system for triaging repair requests in remote Northern Territory public housing, where jobs often wait weeks because of trip costs. The system ranks repairs by urgency, groups nearby communities into shared weekly trips, and explains to tenants why their repair waited. Because no public NT repair dataset exists, the team generated synthetic requests, while geography, house counts and response-time data come from real sources and are labeled accordingly in the demo. The urgency model reaches a ROC-AUC of 0.84 on unseen wording and catches 99.3% of dangerous reports only when combined with human review. Its confidence scores proved poorly calibrated, so the team chose not to show confidence percentages to tenants.

0 comments Read more at DEV Community