3cL1p5e7

import {ActorSubclass} from '@dfinity/agent';
import { useCallback, useEffect, useState } from 'react';
import cryptoJS from 'crypto-js';
import type { _SERVICE } from 'PATH_TO_SERTIFIED_ASSETS_TS_IDL';

export interface UseUploaderProps {
	canister: ActorSubclass<_SERVICE>;
	chunkSize?: number;
	chunksPerOperation?: number;
	progress?(stats: Stats): any;

peterpeterparker

#!/usr/bin/env node

import {writeFile} from 'fs/promises';

import {Blob} from 'node:buffer';

import fetch from 'node-fetch';

const fetchData = async (url) => {
  const response = await fetch(url);

nomeata

Every now and then someone asks whether Motoko canisters can use certified variables, or whether they can serve HTTP requests with certification, and I always responded that yes, Motoko can do that, all that’s missing are a few libraries. But I figured I should put my hand where my mouth is, and actually demonstrate that it’s possible.

So here we go. If you go to https://ce7vw-haaaa-aaaai-aanva-cai.ic0.app/ you will see that

• the URL has no raw in it, so it is certified,
• that the response is actually dynamic; you can leave a message at the bottom of https://ic.rocks/principal/ce7vw-haaaa-aaaai-aanva-cai and see it show up
• this claims it’s written in Motoko.

To prove the latter claim, here is the commented code; you can also browse the full repository.

main.mo

krpeacock

use crate::lib::environment::Environment;
use crate::lib::error::DfxResult;
use crate::lib::ic_attributes::CanisterSettings;
use crate::lib::identity::identity_utils::CallSender;
use crate::lib::identity::Identity;
use crate::lib::models::canister_id_store::CanisterIdStore;
use crate::lib::provider::get_network_context;
use crate::lib::waiter::waiter_with_timeout;

use anyhow::anyhow;

SuddenlyHazel

type Value = 
 variant {
   Bool: bool;
   Class: vec Property;
   Empty;
   Float: float64;
   Int: int;
   Nat: nat;
   Principal: principal;
   Text: text;