>>> from pybtc import * | |
>>> | |
>>> # first step we need create 2 of 3 multisig output and add same btc | |
>>> | |
>>> a1 = Address("cPBuqn4ZsddXunx6EEev6khbfUzFnh3xxdEUPCrm5uy9qGcmbBEt", | |
address_type="P2PKH", testnet=True) | |
>>> a2 = Address("cVgShyj2q4YKFX8VzCffuQcrJVYhp522NFozNi7ih2KgNVbnysKX", | |
address_type="P2PKH", testnet=True) | |
>>> a3 = Address("cQWBhFENcN8bKEBsUHvpCyCfWVHDLfn1M65Gd6nenQkpEqL4DNUH", | |
address_type="P2PKH", testnet=True) |
user@ubuntu:/dev/shm$ ~/fio/fio --loops=5 --size=1g --runtime=10 --stonewall --direct=0 --group_reporting \ | |
--name=SeqQ32T1read --bs=128k --iodepth=32 --rw=read \ | |
--name=SeqQ32T1write --bs=128k --iodepth=32 --rw=write \ | |
--name=4kQ8T8read --bs=4k --iodepth=8 --numjobs=8 --rw=randread \ | |
--name=4kQ8T8write --bs=4k --iodepth=8 --numjobs=8 --rw=randwrite \ | |
--name=4kQ32T1read --bs=4k --iodepth=32 --rw=randread \ | |
--name=4kQ32T1write --bs=4k --iodepth=32 --rw=randwrite \ | |
--name=4kQ1T1read --bs=4k --iodepth=1 --rw=randread \ | |
--name=4kQ1T1write --bs=4k --iodepth=1 --rw=randwrite | |
SeqQ32T1read: (g=0): rw=read, bs=(R) 128KiB-128KiB, (W) 128KiB-128KiB, (T) 128KiB-128KiB, ioengine=psync, iodepth=32 |
pragma solidity ^0.5.8; | |
contract MiMC { | |
uint constant FIELD_SIZE = 21888242871839275222246405745257275088548364400416034343698204186575808495617; | |
function MiMCSponge(uint256 xL, uint256 xR) public pure returns (uint256, uint256) { | |
uint exp; | |
uint t; | |
uint xR_tmp; | |
t = xL; |
Last Updated: March 2023
IMPORTANT: Ignore the out-of-date steps below for getting Chromium keys.
Instead, read this up-to-date guide (Jan 2023) written by @LearningToPi.
P.S. Thank you to every contributor below who provided tips over the years on what should be a straightforward process: setting up Chromium for local development.
Long live the web!
Hence, if you are interested in existing applications to "just work" without the need for adjustments, then you may be better off avoiding Wayland.
Wayland solves no issues I have but breaks almost everything I need. Even the most basic, most simple things (like xkill
) - in this case with no obvious replacement. And usually it stays broken, because the Wayland folks mostly seem to care about Automotive, Gnome, maybe KDE - and alienating everyone else (e.g., people using just an X11 window manager or something like GNUstep) in the process.
Wayland proponents make it seem like Wayland is "the successor" of Xorg, when in fact it is not. It is merely an incompatible alternative, and not even one that has (nor wants to have) feature parity (missing features). And unlike X11 (the X Window System), Wayland protocol designers actively avoid the concept of "windows" (making up incompr