Bitmark Inc.

@bitmarkinc

Bitmark Inc.

Private team

Joined on Dec 9, 2019

  • Feral File Variables For Feral File generative artworks, it injects pre-defined variables then the collector click to view the software artwork in in frame. This helps artists be able to make variants to their artworks. The variables are: blockchain - (bitmark | ethereum | tezos) contract - contract address if any. empty for bitmark token_id - a unique id of a token in the blockchain. It is hex in bitmark and decimal in tezos and ethereum artwork_number - the artwork number of a series starts from 1?? token_id_hash - the sha256 hash of a token ID. edition_number - the edition number of an index starts from zero (legacy only)
     Like  Bookmark
  • For each query of NFTs, we returns tokens in the following format. { "id": "19961", "blockchain": "tezos", "fungible": true, "contractType": "fa2", "contractAddress": "KT1MxDwChiDwd6WBVs24g1NjERUoK622ZEFp", "edition": 0, "editionName": "",
     Like 1 Bookmark
  • Status: Wait for review Reviewer: Sean and Casey Reas Learn from previous contract design. Repository feralfile-exhibition-smart-contract Commit: ff80a5d488e21cf2de3a9db980bde83b1f56952d Files:contracts ├── Authorizable.sol ├── ECDSASigner.sol
     Like  Bookmark
  • Ethereum Token Metadata { "access_artwork_files": "With proof of purchase, access to complete artwork and supplemental material is granted through creating an account on feralfile.com or Feral File’s official web address at the time of purchase. Files are redundantly stored on IPFS. If the official Feral File domain is no longer accessible or active, contact the present-day custodian of Feral File’s archive, the artist studio, or artist estate.", "artist": "An.H4", "artwork_index": 62, "artwork_name": "#63", "attributes": [ { "trait_type": "Exhibition", "value": "Feral File - FF 2.0 144 Sets"
     Like  Bookmark
  • Goal Support buying token on-chain. Support distributing royalties of primary sale on-chain. Related Contract Code struct Artwork { uint256 id uint256 seriesIndex string ipfsCID }
     Like  Bookmark
  • Introduction The Key Management System (KMS) is a core service of the Autonomy app, a secure and user-friendly cryptocurrency wallet. The Autonomy app utilizes the HD Wallet model, following the BIP-44 standard, to derive a master seed that can generate multiple child wallets. Additionally, the app complies to the BIP-39 standard, allowing users to back up their seed as a recovery phrase and use with other wallets. This document aims to provide a comprehensive overview of the Key Management System within the Autonomy app. It will cover the functionality, security measures, and processes involved in managing cryptographic keys and securing user funds. By understanding the KMS, developers and stakeholders can gain insights into the technical aspects of the system and ensure its robustness, security and reliability. Key Management System Overview The Key Management System in the Autonomy app is responsible for generating, storing, and managing cryptographic keys used to secure user funds. It employs the HD Wallet model, based on the BIP-44 standard, to derive a master seed that can generate an unlimited number of child wallets. The system ensures that each child wallet has a unique address and corresponding private key. The KMS also supports the import of recovery phrases from external sources, enabling the management of multiple HD wallets. Recovery Phrase and Key Storage The Autonomy app provides multiple options for backing up and securing the HD wallet seeds. By default, the app employs a technique to store the HD wallet seeds on the iCloud Keychain (on iOS) and Blockstore (on Android). These storages offer end-to-end encryption per device at the operating system level, providing a secure environment for storing the wallet seeds.
     Like  Bookmark
  • To utilize Autonomy app to manage multiple accounts(ethereum, tezos) and use with Feral File, we need to build our own walletconnect, say Autonomy connect, to facilitate the connect and signing process between blockchains. Autonomy account management This is a derivation path of autonomy app 44/0/0/DID 44/0/0/tezos 44/0/0/eth Connect
     Like  Bookmark
  • Signing Here we defines the SPEC of the signing mechanism for validating a meta transaction. Tezos Signing To normalzie the signing data from tezos, we need to pack each signing variables and turn it into bytes. For example, if we want to sign the contract address, we will do let contract_address_bytes = Bytes.pack Tezos.get_self_address in After we have all the variables ready, we then concatenate them into a signing message with a message prefix Tezos Signed Message: and split all variables by the message separator | . For example, if we are going to sign these three variables: contract, tokenID, counter. The signing message will be
     Like  Bookmark
  • Feral File (FF) maintains the sale and is in charge of determining the sale price, sale items and royality amounts based on the sale types (normal sale or auction sale). The contract is only to facilitates payments and tokens distributing according to the sale instrument from FF. Sale Lock To ensure both crypto user and credit card user both have the same opportunity to process the sale, we introduce a sale lock into the system. It is a 3 minutes lock that starts counting down when the purchase process begin. Due to the limit of signature revealing, the purchasing lock will persist until the purchase is fulfill or the time count down to zero. That means each user can only perform a purchasing flow at a time. To ensure the contract function also align with the server lock, there is a expiry time of each sale instrument data. The expiry will set to the end time of the lock for each sale. Pay in Crypto In crypto payments, the collectors will get sale instrument data from FF server. The data includes target tokens in a particular sale and the price of the sale. Users use the data to construct payment transactions and submit it to the blockchain to pay and get tokens directly.
     Like  Bookmark
  • Data Feral File 1.0 Title ID Type Transparent Grit 2a727b17-7890-4464-913d-3fe5ad2af4ae Artwork
     Like  Bookmark
  • Editor of this document: Jason Liu Employee benefits are designed as an extension of our compensation (sustainable living) and ethos (building a company that will last 100 years). You are an owner in Bitmark Inc. You have the ability to make decisions that are best for the company. Share questions or proposals for new benefits with your manager. Expenses Spend the company’s money as if it were your money, paying for things that can help you improve your work such as equipment and education. Provide Nhung (Vietnam) or Agnes (non-Vietnam), with your manager cc'ed, with the amount to be reimbursed towards the end of the month.
     Like  Bookmark
  • Editor of this document: Michael Nguyen Compensation at Bitmark is split into two components: Salary compensation is set to help each employee cultivate a comfortable and sustainable living situation. We don't care about your past compensation or match other companies' offers. We look at industry data as well as investigate local living situations to determine sustainable salary levels. Equity compensation is a reflection of an employee’s long term impact on the success of the company. Salary and local market are not components of equity compensation. Salary Salary compensation is set to help each employee cultivate a comfortable and sustainable living situation.
     Like  Bookmark
  • Direct pay to buy Flow: User pays to buy a token using {Apple,Google} Pay. Autonomy server receives the payment receipts. Autonomy server makes request to fxhash API with a signaturecentralized server to server call fxhash mints to the destination address sequenceDiagram
     Like  Bookmark
  • Editor of this document: Michael Nguyen Culture is what you do and not what you say. Each employee has shared what they strive to do on an everyday basis at Bitmark. Newest contributions go on top. Anais Barthe I don’t make the assumption that everyone should know everything. And I appreciate that across fields people are ready to adapt their vocabulary so knowledge can be shared. I feel that the main motivation towards projects are not money-driven but because they are projects trying to solve questions that matter.
     Like  Bookmark
  • Operations Overview Metrics Tracking Cycles improvements tracking Cycle improvements knowledge base Feral File Github cycle overview Feral File Cycle Results Cycle Folders
     Like  Bookmark
  • Editor of this document: Michael Nguyen Overview Public Positioning Feral File is a space for the new media community to co-create the future of art making, exhibiting, and collecting. Internal Positioning The Feral File online gallery gives collectors access to the world’s most influential artworks because of its artist-first focus on curation. Intro
     Like  Bookmark
  • Artist Feedback Reflections Curator Feedback Reflections
     Like  Bookmark
  • Design Requirement Use bytes as the type of fingerprint the fingerprint bytes currently will be the abi.encode result which comes from ethereum This is to ensure the id will be the same as the ethereum blockchain Provide an authorized_transfer for delegating token transfer from the token owner each transfer request includes a expiry time
     Like  Bookmark
  • Overview The Autonomy app Android version uses the Keystore system to store cryptographic keys (Wallet seeds) and perform signing. One of the downsides of Keystore is lack of backup ability. Thus we could not provide a secured backup method in the app. From the document, the Blockstore provides an end-to-end backup (on capable devices) mechanism in Android. Using it in conjunction with the Keystore, we can achieve the security and redundancy level similar to what iOS offers with the iCloud keychain. Security goals The Wallet keys are backed up safely in independent storage. App deletion and reinstallation won't remove the keys. Only the app (with the correct application signing key associated with the app bundle id) can access the Wallet keys from the storage. The Wallet keys in the storage are encrypted by default and only be accessible when the app requests under user biometric verification.
     Like  Bookmark
  • Editor of this document: Michael Nguyen No set of guidelines can account for every scenario. From principles, Bitmark employees may not use their knowledge or private access to guide their or others' purchasing decisions on Feral File. In application of these principles, Bitmark employees are prohibited from participating in any sale in which Feral File has an information advantage over the public. This includes both direct and indirect participation such as by funding a third party. For example, in highest bidder auctions, Feral File can view collector deposits and use that information to understand upcoming bids - employees cannot partipcate in these auctions. With fixed price sales, however, Feral File has no special access to purchase before others - employees may participate in purchasing.
     Like  Bookmark