kdembler

The first public release of The Terminal will coincide with the start of SQDGN->DSQD token migration. Initially access to The Terminal will be based on this migration and not staking, which will be available only after the migration is finished.

Here's how the migration will look like:

1. We deploy all smart contracts, announce all the dates and details for the community. Migration is in "NotStarted" state.
2. We enable migration deposits. Users can deposit their old (SQDGN) tokens into the migration vault contract. This can be single or multiple deposits per single user. Migration is in "DepositOpen" state.
3. We disable migration deposits, user can no longer deposit SQDGN tokens. Migration is in "DepositClosed" state.
4. We migrate token supply by minting 1B (total supply of SQDGN) DSQD tokens. Migration Vault smart contract will receive 1 DSQD for every 1 SQDGN depositted into it by users. The difference between total supply and tokens migrated (1B - SQDGN balance of MigrationVault) will be sent to projec

kdembler

{"unexpectedLocal":["102794","102795","102822","102913","102914","102915","102946","102947","102950","102953","102954","104607","115035","116888","116890","116926","116927","124844","125020","128287","129359","129360","133579","134414","134680","135546","136552","136553","141265","141266","143052","143053","143379","143380","144440","144779","144838","144839","144966","144989","146454","146703","146712","148496","148497","148500","148501","152864","153216","153979","154164","155288","155420","155421","155438","155451","162004","162369","162452","162453","162482","162483","162505","162506","162517","162518","164300","164331","164332","164584","165057","167802","167803","167852","167870","167871","168302","168303","169026","169434","169435","171595","171865","177065","177066","183232","183774","185170","185282","185972","185973","186968","186969","187002","188397","188398","188399","188400","188732","188733","188734","188735","190085","190086","190117","190118","190119","190120","190121","190122","190123","1901

kdembler

{
  "endpoint": "https://dist1.joyutils.org/distributor/",
  "location": {
    "countryCode": "DE",
    "city": "Nuremberg",
    "coordinates": {
      "latitude": 49.4521,
      "longitude": 11.0767
    }
  },

kdembler

Apps WG Lead Questionnaire

Just to begin with, I think none of those question should be asked about any specific instance (Gleev/l1.media) as they are all generic to Atlas/Orion/Joystream. Remember that Gleev is just Atlas, with some settings tweaked.

How does Gleev count video views?

It's a very simple mechanism. Whenever Atlas user starts video playback, request is sent to Orion that says "I've watched video X" and Orion increments the view count for this video in its database. This is kind of a placeholder solution until something better is available. This issue was discussed many times (Joystream/atlas#539, https://discord.com/channels/811216481340751934/812345044094156811/971774064962195466). This is far from ideal because anyone can easily send this request to Orion, spoofing a video view. To solve this properly something like Gateway Accounts (Joystream/atlas#1388) would be needed and that needs Orion v2. If what you're looking for is a way

kdembler

general:
  appName: 'Atlas' # Application name - used in the copy throughout the app, in index.html, open graph meta tags, etc
  appTwitterId: '@JoystreamDAO' # Twitter handle for the app - used in open graph meta tags in HTML
  appUrl: 'https://play.joystream.org' # URL at which the app is hosted - used in open graph meta tags in HTML
  pioneerMemberUrlPrefix: 'https://dao.joystream.org/#/members' # URL prefix for Pioneer member profile page - used to link to member details
  joystreamLandingPageUrl: 'https://www.joystream.org' # URL for Joystream landing page - used in the footer and in "Learn more" links
  joystreamDiscordUrl: 'https://discord.gg/DE9UN3YpRP' # URL for Joystream Discord - used for support when errors occur
  atlasGithubUrl: 'https://github.com/Joystream/atlas' # URL for Atlas GitHub repository - used in the footer

storage:

kdembler

Recruitment project - ENS lookup dashboard

Intro

ENS (Ethereum Name Service) enables decentralized usernames based on Ethereum smart contracts. Domain names (e.g. joystream.eth) can be registered with an Ethereum transaction and can be used to resolve an Ethereum address (just like you would resolve an IP address via a DNS).

Task

Your task is to build a simple ENS dashboard that has the following functionalities:

kdembler

import { babel } from '@rollup/plugin-babel'
import graphql from '@rollup/plugin-graphql'
import inject from '@rollup/plugin-inject'
import reactRefresh from '@vitejs/plugin-react-refresh'
import path from 'path'
import { visualizer } from 'rollup-plugin-visualizer'
import { defineConfig } from 'vite'

// https://vitejs.dev/config/
export default defineConfig({

kdembler

Testing dev Atlas

Thanks for your interest in helping test the beta version of Atlas. If you get lost at any point feel free to reach out to me for help on Discord.

Steps to take

1. Go to https://play.joystream.org and open the browser console. (F12 in most browsers)
2. Copy this 👇🏻 and paste it into console. Hit enter. This should result in .json file being downloaded. This contains all your local Atlas state (nothing confidential)

const exportStorage = () => {

kdembler

import { Bytes, Raw } from "@polkadot/types";

import { ChannelMetadata } from "@joystream/content-metadata-protobuf";
import { ChannelCreationParameters } from "@joystream/types/content";

// getApi, getAssets, getRewardAccount and getMetaFromEvent are stubs here

const api = await getApi();

kdembler

Keybase proof

I hereby claim:

• I am kdembler on github.
• I am kdembler (https://keybase.io/kdembler) on keybase.
• I have a public key ASBJlMzsHq4pFmZXo1FN2rzZUA0evz-05jnHKx2ne_oTbgo

To claim this, I am signing this object: