Skip to main content
100%

Exploring smart contract with a web interface using Ethereum and solidity for the Blockchain workshop at iMAL

✓ Published0🌍 Public
UUtopiah
Last edited Nov 6, 2016
Created on Nov 6, 2016

This example demonstrates a web interface for exploring a smart contract on the Ethereum blockchain, showing account balances, block information, and gas prices retrieved via the Web3.js API. It initializes a connection to an Ethereum node, queries the first four accounts and their balances, and displays details about the latest block and available compilers. The code then defines a ballot contract using an ABI and includes the compiled bytecode for deploying it, enabling interactive voting and delegation functions within the browser.

AI-generated description

Similar vizzes

Loading thumbnail…

Working on Solidity Practise

This example shows a Solidity smart contract collection practicing basic syntax, data structures, and functions, with a second contract focused on mapping and struct access patterns. The main contract implements arithmetic operations, comparisons with events, summation loops, modifiers with require statements, and a mark-tracking system that calculates percentages from stored struct arrays. It uses Solidity’s built-in types, modifiers, events, and the `log1` low-level logging function, while the mapping contract demonstrates private state variables and public add/access functions. The code highlights common Solidity patterns like struct initialization, visibility qualifiers, and data location requirements, though the getter for a struct currently fails due to missing memory specification.

NNikhilkuyya
56% match
Loading thumbnail…

Gist 4dd85693f71aa8cb49b95371c091b29a

This example verifies a Blockstack ID by displaying its associated blockchain address. It shows a static confirmation message, linking the ID to the address 1934iXrpvRwM43m1sKhb5cfsrjfUWKH362 with a clickable URL to the Blockstack explorer. The visualization uses plain HTML text and a hyperlink, with no graphical or interactive data-rendering code. The underlying data is the literal address string embedded in the gist file, and the rendering approach is standard web markup without any JavaScript libraries or canvas APIs.

YYannael
55% match
Loading thumbnail…

The code in this gist isn't as succinct as I'd like it to be. Please bare with me and ask plenty of questions that you may have about it.

This example implements a minimal blockchain visualization server using Flask, exposing endpoints to submit transactions, retrieve the current chain, and mine new blocks. The code defines a Block class with SHA-256 hashing and a proof-of-work algorithm that increments values until divisible by 9 and the previous proof. It includes consensus logic to compare chain lengths across peer nodes via HTTP GET requests. The visualization aspect is limited to JSON responses of block data, with no graphical rendering or front-end library in use.

SSassOnTheRoad
54% match
Loading thumbnail…

Gist 7a4aa931c2aa66a9be73b0d0219ae57a

This visualization demonstrates a network graph of Blockstack ID verifications, mapping relationships between cryptographic addresses and their associated identities. It uses d3.forceSimulation to position nodes and links, with each node representing a blockchain address or ID and edges showing verification connections. The graph renders via SVG paths and circles, with color and size encoding node attributes like address type or verification status. Data comes from the Blockstack explorer API, pulling address and verification details from the public blockchain. The visualization updates dynamically as the simulation runs, letting users explore the interconnected web of verified identities.

UUtopiah
53% match
Loading thumbnail…

Gist d85e660d17b58a7ffd73b56a9d5dfb65

This example verifies a Blockstack ID by displaying a fixed blockchain address in a plain-text file. The visualization shows a single static text line confirming the address, with no graphical rendering. It relies solely on the Blockstack Explorer API link embedded in the file to prove ownership of the ID. No data libraries or rendering code are used; the content is pure text. The address is presented as the primary output, with the explorer link as the verification method.

YYannael
51% match
Loading thumbnail…

Created using remix-ide: Realtime Ethereum Contract Compiler and Runtime. Load this file by pasting this gists URL or ID at https://remix.ethereum.org/#version=soljson-v0.6.12+commit.27d51765.js&optimize=false&gist=

This example demonstrates a blockchain-based Know Your Customer (KYC) system implemented in Solidity, showing how customer records are stored, added, removed, and modified through a smart contract. The interface `IKYC` defines the core operations, while the `KYC` contract manages a mapping of customer data, including username, associated data string, and the bank address that initiated the transaction. The code uses `KYCTypes` library to structure bank and customer information, with functions like `addCustomer`, `removeCustomer`, and `modifyCustomer` exposing state changes. The visualization highlights the contract’s runtime behavior, reflecting the Ethereum compiler and execution environment via remix-ide.

NNikhilkuyya
51% match
Loading thumbnail…

Gist 671a9b9586430094aa6d

A web development contract between a cartographer and a turf products company is visualized as a structured, legal timeline. The example uses a custom JavaScript visualization built with D3.js, laying out contract clauses, payment schedules, and milestones as interactive nodes and links. It renders the contract’s text into a diagrammatic flow, with d3.forceSimulation positioning clauses and deadlines, while hover states reveal the original document’s wording. The data source is the raw Markdown contract file, parsed to extract sections, parties, and dates.

SStephen
50% match
Loading thumbnail…

WebAssembly integer operations

This example demonstrates a JavaScript WebAssembly module that exports integer division and echo functions, highlighting a discrepancy between WebAssembly’s spec-defined `ToWebAssemblyValue` coercion and its inverse `ToJSValue` conversion for i32 values. It uses the WebAssembly JavaScript API’s `instantiate` and `instance.exports` to call compiled wasm functions, while manually implementing the ECMA-262 `ToInt32` algorithm and a guessed JavaScript conversion. The visualization presents console output comparing wasm results against equivalent JavaScript conversions, revealing that unsigned division produces different values due to overflow handling.

CColinEberhardt
48% match