Bitcoin Mining Pool Bitcoin.com

[ANN][ANDROID MINING][AIRDROP] NewEnglandcoin: Scrypt RandomSpike

New England
New England 6 States Songs: https://www.reddit.com/newengland/comments/er8wxd/new_england_6_states_songs/
NewEnglandcoin
Symbol: NENG
NewEnglandcoin is a clone of Bitcoin using scrypt as a proof-of-work algorithm with enhanced features to protect against 51% attack and decentralize on mining to allow diversified mining rigs across CPUs, GPUs, ASICs and Android phones.
Mining Algorithm: Scrypt with RandomSpike. RandomSpike is 3rd generation of Dynamic Difficulty (DynDiff) algorithm on top of scrypt.
1 minute block targets base difficulty reset: every 1440 blocks subsidy halves in 2.1m blocks (~ 2 to 4 years) 84,000,000,000 total maximum NENG 20000 NENG per block Pre-mine: 1% - reserved for dev fund ICO: None RPCPort: 6376 Port: 6377
NewEnglandcoin has dogecoin like supply at 84 billion maximum NENG. This huge supply insures that NENG is suitable for retail transactions and daily use. The inflation schedule of NengEnglandcoin is actually identical to that of Litecoin. Bitcoin and Litecoin are already proven to be great long term store of value. The Litecoin-like NENG inflation schedule will make NewEnglandcoin ideal for long term investment appreciation as the supply is limited and capped at a fixed number
Bitcoin Fork - Suitable for Home Hobbyists
NewEnglandcoin core wallet continues to maintain version tag of "Satoshi v0.8.7.5" because NewEnglandcoin is very much an exact clone of bitcoin plus some mining feature changes with DynDiff algorithm. NewEnglandcoin is very suitable as lite version of bitcoin for educational purpose on desktop mining, full node running and bitcoin programming using bitcoin-json APIs.
The NewEnglandcoin (NENG) mining algorithm original upgrade ideas were mainly designed for decentralization of mining rigs on scrypt, which is same algo as litecoin/dogecoin. The way it is going now is that NENG is very suitable for bitcoin/litecoin/dogecoin hobbyists who can not , will not spend huge money to run noisy ASIC/GPU mining equipments, but still want to mine NENG at home with quiet simple CPU/GPU or with a cheap ASIC like FutureBit Moonlander 2 USB or Apollo pod on solo mining setup to obtain very decent profitable results. NENG allows bitcoin litecoin hobbyists to experience full node running, solo mining, CPU/GPU/ASIC for a fun experience at home at cheap cost without breaking bank on equipment or electricity.
MIT Free Course - 23 lectures about Bitcoin, Blockchain and Finance (Fall,2018)
https://www.youtube.com/playlist?list=PLUl4u3cNGP63UUkfL0onkxF6MYgVa04Fn
CPU Minable Coin Because of dynamic difficulty algorithm on top of scrypt, NewEnglandcoin is CPU Minable. Users can easily set up full node for mining at Home PC or Mac using our dedicated cheetah software.
Research on the first forked 50 blocks on v1.2.0 core confirmed that ASIC/GPU miners mined 66% of 50 blocks, CPU miners mined the remaining 34%.
NENG v1.4.0 release enabled CPU mining inside android phones.
Youtube Video Tutorial
How to CPU Mine NewEnglandcoin (NENG) in Windows 10 Part 1 https://www.youtube.com/watch?v=sdOoPvAjzlE How to CPU Mine NewEnglandcoin (NENG) in Windows 10 Part 2 https://www.youtube.com/watch?v=nHnRJvJRzZg
How to CPU Mine NewEnglandcoin (NENG) in macOS https://www.youtube.com/watch?v=Zj7NLMeNSOQ
Decentralization and Community Driven NewEnglandcoin is a decentralized coin just like bitcoin. There is no boss on NewEnglandcoin. Nobody nor the dev owns NENG.
We know a coin is worth nothing if there is no backing from community. Therefore, we as dev do not intend to make decision on this coin solely by ourselves. It is our expectation that NewEnglandcoin community will make majority of decisions on direction of this coin from now on. We as dev merely view our-self as coin creater and technical support of this coin while providing NENG a permanent home at ShorelineCrypto Exchange.
Twitter Airdrop
Follow NENG twitter and receive 100,000 NENG on Twitter Airdrop to up to 1000 winners
Graphic Redesign Bounty
Top one award: 90.9 million NENG Top 10 Winners: 500,000 NENG / person Event Timing: March 25, 2019 - Present Event Address: NewEnglandcoin DISCORD at: https://discord.gg/UPeBwgs
Please complete above Twitter Bounty requirement first. Then follow Below Steps to qualify for the Bounty: (1) Required: submit your own designed NENG logo picture in gif, png jpg or any other common graphic file format into DISCORD "bounty-submission" board (2) Optional: submit a second graphic for logo or any other marketing purposes into "bounty-submission" board. (3) Complete below form.
Please limit your submission to no more than two total. Delete any wrongly submitted or undesired graphics in the board. Contact DISCORD u/honglu69#5911 or u/krypton#6139 if you have any issues.
Twitter Airdrop/Graphic Redesign bounty sign up: https://goo.gl/forms/L0vcwmVi8c76cR7m1
Milestones
Roadmap
NENG v1.4.0 Android Mining, randomSpike Evaluation https://github.com/ShorelineCrypto/NewEnglandCoin/releases/download/NENG_2020_Q3_report/NENG_2020_Q3_report.pdf
RandomSpike - NENG core v1.3.0 Hardfork Upgrade Proposal https://github.com/ShorelineCrypto/NewEnglandCoin/releases/download/2020Q1_Report/Scrypt_RandomSpike_NENGv1.3.0_Hardfork_Proposal.pdf
NENG Security, Decentralization & Valuation
https://github.com/ShorelineCrypto/NewEnglandCoin/releases/download/2019Q2_report/NENG_Security_Decentralization_Value.pdf
Whitepaper v1.0 https://github.com/ShorelineCrypto/NewEnglandCoin/releases/download/whitepaper_v1.0/NENG_WhitePaper.pdf
DISCORD https://discord.gg/UPeBwgs
Explorer
http://www.findblocks.com/exploreNENG http://86.100.49.209/exploreNENG http://nengexplorer.mooo.com:3001/
Step by step guide on how to setup an explorer: https://github.com/ShorelineCrypto/nengexplorer
Github https://github.com/ShorelineCrypto/NewEnglandCoin
Wallet
Android with UserLand App (arm64/armhf), Chromebook (x64/arm64/armhf): https://github.com/ShorelineCrypto/NewEnglandCoin/releases/tag/v1.4.0.5
Linux Wallet (Ubuntu/Linux Mint, Debian/MX Linux, Arch/Manjaro, Fedora, openSUSE): https://github.com/ShorelineCrypto/NewEnglandCoin/releases/tag/v1.4.0.3
MacOS Wallet (10.11 El Capitan or higher): https://github.com/ShorelineCrypto/NewEnglandCoin/releases/tag/v1.4.0.2
Android with GNUroot on 32 bits old Phones (alpha release) wallet: https://github.com/ShorelineCrypto/NewEnglandCoin/releases/tag/v1.4.0
Windows wallet: https://github.com/ShorelineCrypto/NewEnglandCoin/releases/tag/v1.3.0.1
addnode ip address for the wallet to sync faster, frequently updated conf file: https://github.com/ShorelineCrypto/cheetah_cpumineblob/mastenewenglandcoin.conf-example
How to Sync Full Node Desktop Wallet https://www.reddit.com/NewEnglandCoin/comments/er6f0q/how_to_sync_full_node_desktop_wallet/
TWITTER https://twitter.com/newenglandcoin
REDDIT https://www.reddit.com/NewEnglandCoin/
Cheetah CPU Miner Software https://github.com/ShorelineCrypto/cheetah_cpuminer
Solo Mining with GPU or ASIC https://bitcointalk.org/index.php?topic=5027091.msg52187727#msg52187727
How to Run Two Full Node in Same Desktop PC https://bitcointalk.org/index.php?topic=5027091.msg53581449#msg53581449
ASIC/GPU Mining Pools Warning to Big ASIC Miners Due to DynDiff Algo on top of Scrypt, solo mining is recommended for ASIC/GPU miners. Further more, even for mining pools, small mining pool will generate better performance than big NENG mining pool because of new algo v1.2.x post hard fork.
The set up configuration of NENG for scrypt pool mining is same as a typical normal scrypt coin. In other word, DynDiff on Scrypt algo is backward compatible with Scrypt algo. Because ASIC/GPU miners rely on CPU miners for smooth blockchain movement, checkout bottom of "Latest News" section for A WARNING to All ASIC miners before you decide to dump big ASIC hash rate into NENG mining.
(1) Original DynDiff Warning: https://bitcointalk.org/index.php?topic=5027091.msg48324708#msg48324708 (2) New Warning on RandomSpike Spike difficulty (244k) introduced in RandomSpike served as roadblocks to instant mining and provide security against 51% attack risk. However, this spike difficulty like a roadblock that makes big ASIC mining less profitable. In case of spike block to be mined, the spike difficulty immediately serve as base difficulty, which will block GPU/ASIC miners effectively and leave CPU cheetah solo miners dominating mining almost 100% until next base difficulty reset.
FindBlocks http://findblocks.com/
CRpool http://crpool.xyz/
Cminors' Pool http://newenglandcoin.cminors-pool.com/
SPOOL https://spools.online/
Exchange
📷
https://shorelinecrypto.com/
Features: anonymous sign up and trading. No restriction or limit on deposit or withdraw.
The trading pairs available: NewEnglandcoin (NENG) / Dogecoin (DOGE)
Trading commission: A round trip trading will incur 0.10% trading fees in average. Fees are paid only on buyer side. buy fee: 0.2% / sell fee: 0% Deposit fees: free for all coins Withdraw fees: ZERO per withdraw. Mining fees are appointed by each coin blockchain. To cover the blockchain mining fees, there is minimum balance per coin per account: * Dogecoin 2 DOGE * NewEnglandcoin 1 NENG
Latest News Aug 30, 2020 - NENG v1.4.0.5 Released for Android/Chromebook Upgrade with armhf, better hardware support https://bitcointalk.org/index.php?topic=5027091.msg55098029#msg55098029
Aug 11, 2020 - NENG v1.4.0.4 Released for Android arm64 Upgrade / Chromebook Support https://bitcointalk.org/index.php?topic=5027091.msg54977437#msg54977437
Jul 30, 2020 - NENG v1.4.0.3 Released for Linux Wallet Upgrade with 8 Distros https://bitcointalk.org/index.php?topic=5027091.msg54898540#msg54898540
Jul 21, 2020 - NENG v1.4.0.2 Released for MacOS Upgrade with Catalina https://bitcointalk.org/index.php?topic=5027091.msg54839522#msg54839522
Jul 19, 2020 - NENG v1.4.0.1 Released for MacOS Wallet Upgrade https://bitcointalk.org/index.php?topic=5027091.msg54830333#msg54830333
Jul 15, 2020 - NENG v1.4.0 Released for Android Mining, Ubuntu 20.04 support https://bitcointalk.org/index.php?topic=5027091.msg54803639#msg54803639
Jul 11, 2020 - NENG v1.4.0 Android Mining, randomSpike Evaluation https://bitcointalk.org/index.php?topic=5027091.msg54777222#msg54777222
Jun 27, 2020 - Pre-Announce: NENG v1.4.0 Proposal for Mobile Miner Upgrade, Android Mining Start in July 2020 https://bitcointalk.org/index.php?topic=5027091.msg54694233#msg54694233
Jun 19, 2020 - Best Practice for Futurebit Moonlander2 USB ASIC on solo mining mode https://bitcointalk.org/index.php?topic=5027091.msg54645726#msg54645726
Mar 15, 2020 - Scrypt RandomSpike - NENG v1.3.0.1 Released for better wallet syncing https://bitcointalk.org/index.php?topic=5027091.msg54030923#msg54030923
Feb 23, 2020 - Scrypt RandomSpike - NENG Core v1.3.0 Relased, Hardfork on Mar 1 https://bitcointalk.org/index.php?topic=5027091.msg53900926#msg53900926
Feb 1, 2020 - Scrypt RandomSpike Proposal Published- NENG 1.3.0 Hardfork https://bitcointalk.org/index.php?topic=5027091.msg53735458#msg53735458
Jan 15, 2020 - NewEnglandcoin Dev Team Expanded with New Kickoff https://bitcointalk.org/index.php?topic=5027091.msg53617358#msg53617358
Jan 12, 2020 - Explanation of Base Diff Reset and Effect of Supply https://www.reddit.com/NewEnglandCoin/comments/envmo1/explanation_of_base_diff_reset_and_effect_of/
Dec 19, 2019 - Shoreline_tradingbot version 1.0 is released https://bitcointalk.org/index.php?topic=5121953.msg53391184#msg53391184
Sept 1, 2019 - NewEnglandcoin (NENG) is Selected as Shoreline Tradingbot First Supported Coin https://bitcointalk.org/index.php?topic=5027091.msg52331201#msg52331201
Aug 15, 2019 - Mining Update on Effect of Base Difficulty Reset, GPU vs ASIC https://bitcointalk.org/index.php?topic=5027091.msg52169572#msg52169572
Jul 7, 2019 - CPU Mining on macOS Mojave is supported under latest Cheetah_Cpuminer Release https://bitcointalk.org/index.php?topic=5027091.msg51745839#msg51745839
Jun 1, 2019 - NENG Fiat project is stopped by Square, Inc https://bitcointalk.org/index.php?topic=5027091.msg51312291#msg51312291
Apr 21, 2019 - NENG Fiat Project is Launched by ShorelineCrypto https://bitcointalk.org/index.php?topic=5027091.msg50714764#msg50714764
Apr 7, 2019 - Announcement of Fiat Project for all U.S. Residents & Mobile Miner Project Initiation https://bitcointalk.org/index.php?topic=5027091.msg50506585#msg50506585
Apr 1, 2019 - Disclosure on Large Buying on NENG at ShorelineCrypto Exchange https://bitcointalk.org/index.php?topic=5027091.msg50417196#msg50417196
Mar 27, 2019 - Disclosure on Large Buying on NENG at ShorelineCrypto Exchange https://bitcointalk.org/index.php?topic=5027091.msg50332097#msg50332097
Mar 17, 2019 - Disclosure on Large Buying on NENG at ShorelineCrypto Exchange https://bitcointalk.org/index.php?topic=5027091.msg50208194#msg50208194
Feb 26, 2019 - Community Project - NewEnglandcoin Graphic Redesign Bounty Initiated https://bitcointalk.org/index.php?topic=5027091.msg49931305#msg49931305
Feb 22, 2019 - Dev Policy on Checkpoints on NewEnglandcoin https://bitcointalk.org/index.php?topic=5027091.msg49875242#msg49875242
Feb 20, 2019 - NewEnglandCoin v1.2.1 Released to Secure the Hard Kork https://bitcointalk.org/index.php?topic=5027091.msg49831059#msg49831059
Feb 11, 2019 - NewEnglandCoin v1.2.0 Released, Anti-51% Attack, Anti-instant Mining after Hard Fork https://bitcointalk.org/index.php?topic=5027091.msg49685389#msg49685389
Jan 13, 2019 - Cheetah_CpuMiner added support for CPU Mining on Mac https://bitcointalk.org/index.php?topic=5027091.msg49218760#msg49218760
Jan 12, 2019 - NENG Core v1.1.2 Released to support MacOS OSX Wallet https://bitcointalk.org/index.php?topic=5027091.msg49202088#msg49202088
Jan 2, 2019 - Cheetah_Cpuminer v1.1.0 is released for both Linux and Windows https://bitcointalk.org/index.php?topic=5027091.msg49004345#msg49004345
Dec 31, 2018 - Technical Whitepaper is Released https://bitcointalk.org/index.php?topic=5027091.msg48990334#msg48990334
Dec 28, 2018 - Cheetah_Cpuminer v1.0.0 is released for Linux https://bitcointalk.org/index.php?topic=5027091.msg48935135#msg48935135
Update on Dec 14, 2018 - NENG Blockchain Stuck Issue https://bitcointalk.org/index.php?topic=5027091.msg48668375#msg48668375
Nov 27, 2018 - Exclusive for PC CPU Miners - How to Steal a Block from ASIC Miners https://bitcointalk.org/index.php?topic=5027091.msg48258465#msg48258465
Nov 28, 2018 - How to CPU Mine a NENG block with window/linux PC https://bitcointalk.org/index.php?topic=5027091.msg48298311#msg48298311
Nov 29, 2018 - A Warning to ASIC Miners https://bitcointalk.org/index.php?topic=5027091.msg48324708#msg48324708
Disclosure: Dev Team Came from ShorelineCrypto, a US based Informatics Service Business offering Fee for service for Coin Creation, Coin Exchange Listing, Blockchain Consulting, etc.
submitted by honglu69 to NewEnglandCoin [link] [comments]

down the Node-Red rabbit hole, part 5 - hold my beer

part1 part2 part3 part4
so, it's been 4 months since i started this journey and i gotta say that NR has really re-vitalized my personal interest in home-automation, as well as, my HA and whole house setup.
i've done more in the past 4 months, to streamline my setup and adding new automations than i've done in the three years since i started using HA somewhere around v0.24.x'ish. i got that shit dialed in now.
(also some credit to EspHome for being awesome, despite having meh documentation. yeah, i said it. meh👏doc👏u👏men👏ta👏shun)
at this point i have about 36 NR tabs. some are just testing, or playing around with a particular component/palette, but most have at least one flow on it that is live and in use.
so, i thought i'd break some of them down for you guys, 'barney style+':
(also, some of these are way to huge to post readable screenshots of, so i'm just gonna describe them. plus some of these i detailed in my previous posts.)
first up is my globals. where i set global.vars
arrive/away
morning/bedtime/naptime
alarm
sonos
ping
watchdog
battery (the nodes are very similar to above)
switch control
harmony
remote
long term away
spotify
washedryer
doorbell
disk space
gmail
calendar
alexa TTS (subflow)
drafthouse
twitter link
so, yeah. i'd like to see some of you post some of your flows/ideas if only so i could totally steal them.
.
.
+obscure skippy joke. it's from a book++.
++yes i read. well, i audiobook, but same diff+++.
+++i mean, it's just basic science!++++
++++i mean, that study coulda been bullshit, sponsored by "the audiobook council" or some shit, but i'm taking it at face value.
submitted by stoneobscurity to homeassistant [link] [comments]

part 3: down the NodeRed rabbit hole - resurrection (long)

so, now that i've got about 4 weeks of NR experience under my belt, i thought i would do a follow up and show a few new flows. plus, i've picked up a few new hardware add-ons. namely a Harmony Hub and a coupla Sonoff/Tasmota S31.
one of the new things i did was setup some global.variables i can use in any flow.
https://imgur.com/YFJEwRd
1] is pretty obvious, does my bayesian sensors think i'm home/not_home, and then save it to a global.variable.
2] reads the MQTT for my S31 power monitor on my dumb TV. if it's > 100, then the TV is ON, <= 99, then TV is OFF (or in the process of turning off). then set a global.variable for on/off.
https://imgur.com/mcuS1Vk
3] i changed the day/night temperatures to global.variables.
4] this one gets the current volume level of my Sonos and then stores that to a global.variable. (get to why further below)
5] this one i talked about in another post here: https://www.reddit.com/homeassistant/comments/abvqup/device_tracker_with_unifi2mqtt/
okay, so now that i know if my dumb TV is on/off, then i can add it into my "away" (and "bedtime") flow. that gray one on the bottom right is using the HarmonyHub control node to fire the power toggle. (which i'll get to further below) plus it'll stop my Sonos, if it's playing.
https://imgur.com/nerbMv3
also you may notice the "alexa TTS" one, that's a subflow, which is a bit of reusable flow, you can put anywhere you want it. this one picks a random number between 1 and 10, then alexa TTS plays the corresponding message.
https://imgur.com/bLtBlaD
this was also my attempt to get alexa to say "aaaf-firmative" like newt in aliens.
https://imgur.com/cUnG1IE
doesn't really work, but i'm determined to make this happen. gonna have to figure out the proper phonetics of it. then i'm totally gonna get her to do a stutter like max headroom on one of the other responses. but, my ultimate goal is to get her to do "twiki" from buck rogers. beaty beaty
anyways, i've also added that subflow to all my switch on/offs. along with an MQTT log.
https://imgur.com/SnpAnW8
now for some of the new stuff...
here's a sleep timer. if i'm listening to music in bed, i can activate this with "alexa turn on sleep" and what it does, is it takes the current volume level of my Sonos, stored in a global.var, stores it in a flow.var, then subtracts 1 every minute, until it reaches zero. if the volume is at 30, then it'll be 30 mins until zero.
https://imgur.com/7QmbY2S
once it reaches zero, it stops the music, sets the volume back to the original state (ie: 30) and then turns itself off.
there's an issue when you use something like a Harmony Hub to turn on/off dumb devices via input_bool, or switches, or lights, etc.: that once you turn it on via NR, HA, HHub, Alexa, etc., then HA thinks it's on. if you then turn it off via the device remote, HA won't let you turn it on again, because HA thinks its already on.
so, i had to use a script and a "dummy" input_boolean. by dummy i mean, that i do not care, and will not EVER care, what it's state is. on. off. whatever. won't need it. it just needs to be there for the script to work.
input_boolean: mac_x: game_x: candles_x: tv_x: 
hide them from emu_hue, cause Alexa doesn't need to see them either.
emulated_hue: host_ip: 10.xx.xx.xx exposed_domains: - input_boolean - script entities: input_boolean.tv_x: hidden: true input_boolean.mac_x: hidden: true input_boolean.candles_x: hidden: true input_boolean.game_x: hidden: true 
add some scripts.
script: tv: alias: "TV" sequence: service: input_boolean.toggle entity_id: input_boolean.tv_x game: alias: "Game" sequence: service: input_boolean.toggle entity_id: input_boolean.game_x mac: alias: "Mac" sequence: service: input_boolean.toggle entity_id: input_boolean.mac_x candles: alias: "Candles" sequence: service: input_boolean.toggle entity_id: input_boolean.candles_x 
so instead of key'ing off the input_booleans, i key off the script call. "alexa, turn on candles" calls the script, which toggles the i_b but i only care about the state change of the script. then NR does it's thing.
https://imgur.com/Hky9fWd
notice tho, that it's a little smart. if the tv is already on, via that global.var, then it just switches inputs, otherwise it turns it on, waits 7 seconds, then switches inputs.
okay, here's something REALLY advanced.
i have a second pi running cgminer with a USB hub and some USB stick ASIC bitcoin miners. and every once and a while, they stop working and need to be reset. and you can't just restart, you gotta kill the power to the hubs to get them to reset. and then restart cgminer.
enter NR cgminer node and the cgminer API.
https://imgur.com/POSkjrp
so every 5 mins, hit the cgminer API, it returns stats in json, dump those to mqtt. use the function node to pull out the array nested values we need to look at. look for a zero value in any of them. if the input_boolean "auto-reset-miner" is on, then lets reset.
stop cgminer, wait, turn off the USB hub, wait, turn on hub, wait, start cgminer, send an alert to mqtt and SMS me.
now the real magic is the red exec "start cgminer" node. because we stopped cgminer, we have to start it again, on a whole other computer than NR is on.
it basically does a SSH into the miner pi and starts up cgminer. this was difficult to accomplish inside a docker of NR. i had to move some ssh keys around and then reference them with full paths. then i had to do an ssh-copy-id so it didn't require a password.
ssh -i /data/.ssh/id_rsa [email protected] "start cgminer commands" 
anyways, i'm really proud of this one. it was difficult to figure out how to make it work. lots of different moving parts coming together.
here's something i'm still working on. a remote control using the NR dashboard UI.
https://imgur.com/nkRpAsf
something i can just put an icon on my iphone home screen and use from the couch.
https://imgur.com/maeJm0Q
anyways, enjoy.
or don't. i'm not your cruise director.
you do you.
part 1 https://www.reddit.com/homeassistant/comments/a61ro9/so_i_went_down_the_nodered_rabbit_hole_long/
part 2 https://www.reddit.com/homeassistant/comments/a6jz92/nodered_rabbit_hole_part_2/
submitted by stoneobscurity to homeassistant [link] [comments]

Initially, I liked SegWit. But then I learned SegWit-as-a-SOFT-fork is dangerous (making transactions "anyone-can-spend"??) & centrally planned (1.7MB blocksize??). Instead, Bitcoin Unlimited is simple & safe, with MARKET-BASED BLOCKSIZE. This is why more & more people have decided to REJECT SEGWIT.

Initially, I liked SegWit. But then I learned SegWit-as-a-SOFT-fork is dangerous (making transactions "anyone-can-spend"??) & centrally planned (1.7MB blocksize??). Instead, Bitcoin Unlimited is simple & safe, with MARKET-BASED BLOCKSIZE. This is why more & more people have decided to REJECT SEGWIT.
Summary
Like many people, I initially loved SegWit - until I found out more about it.
I'm proud of my open-mindedness and my initial - albeit short-lived - support of SegWit - because this shows that I judge software on its merits, instead of being some kind of knee-jerk "hater".
SegWit's idea of "refactoring" the code to separate out the validation stuff made sense, and the phrase "soft fork" sounded cool - for a while.
But then we all learned that:
And we also got much better solutions: such as market-based blocksize with Bitcoin Unlimited - way better than SegWit's arbitrary, random centrally-planned, too-little-too-late 1.7MB "max blocksize".
This is why more and more people are rejecting SegWit - and instead installing Bitcoin Unlimited.
In my case, as I gradually learned about the disastrous consequences which SegWit-as-a-soft-fork-hack would have, my intial single OP in December 2015 expressing outspoken support for SegWit soon turned to an avalanche of outspoken opposition to SegWit.
Details
Core / Blockstream lost my support on SegWit - and it's all their fault.
How did Core / Blockstream turn me from an outspoken SegWit supporter to an outspoken SegWit opponent?
It was simple: They made the totally unnecessary (and dangerous) decision to program SegWit as a messy and dangerous soft-fork which would:
  • create a massive new threat vector by making all transactions "anyone-can-spend";
  • force yet-another random / arbitrary / centrally planned "max blocksize" on everyone (previously 1 MB, now 1.7MB - still pathetically small and hard-coded!).
Meanwhile, new, independent dev teams which are smaller and much better than the corrupt, fiat-financed Core / Blockstream are offering simpler and safer solutions which are much better than SegWit:
  • For blocksize governance, we now have market-based blocksize based on emergent consensus, provided by Bitcoin Unlimited.
  • For malleability and quadratic hashing time (plus a future-proof, tag-based language similar to JSON or XML supporting much cleaner upgrades long-term), we now have Flexible Transactions (FlexTrans).
This is why We Reject SegWit because "SegWit is the most radical and irresponsible protocol upgrade Bitcoin has faced in its history".
My rapid evolution on SegWit - as I discovered its dangers (and as we got much better alternatives, like Bitcoin Unlimited + FlexTrans):
Initially, I was one of the most outspoken supporters of SegWit - raving about it in the following OP which I posted (on Monday, December 7, 2015) immediately after seeing a presentation about it on YouTube by Pieter Wuille at one of the early Bitcoin scaling stalling conferences:
https://np.reddit.com/btc/comments/3vt1ov/pieter_wuilles_segregated_witness_and_fraud/
Pieter Wuille's Segregated Witness and Fraud Proofs (via Soft-Fork!) is a major improvement for scaling and security (and upgrading!)
I am very proud of that initial pro-SegWit post of mine - because it shows that I have always been totally unbiased and impartial and objective about the ideas behind SegWit - and I have always evaluated it purely on its merits (and demerits).
So, I was one of the first people to recognize the positive impact which the ideas behind SegWit could have had (ie, "segregating" the signature information from the sender / receiver / amount information) - if SegWit had been implemented by an honest dev team that supports the interests of the Bitcoin community.
However, we've learned a lot since December 2015. Now we know that Core / Blockstream is actively working against the interests of the Bitcoin community, by:
  • trying to force their political and economic viewpoints onto everyone else by "hard-coding" / "bundling" some random / arbitrary / centrally-planned 1.7MB "max blocksize" (?!?) into our code;
  • trying to take away our right to vote via a clean and safe "hard fork";
  • trying to cripple our code with dangerous "technical debt" - eg their radical and irresponsible proposal to make all transactions "anyone-can-spend".
This is the mess of SegWit - which we all learned about over the past year.
So, Core / Blockstream blew it - bigtime - losing my support for SegWit, and the support of many others in the community.
We might have continued to support SegWit if Core / Blockstream had not implemented it as a dangerous and dirty soft fork.
But Core / Blockstream lost our support - by attempting to implement SegWit as a dangerous, anti-democratic soft fork.
The lesson here for Core/Blockstream is clear:
Bitcoin users are not stupid.
Many of us are programmers ourselves, and we know the difference between a simple & safe hard fork and a messy & dangerous soft fork.
And we also don't like it when Core / Blockstream attempts to take away our right to vote.
And finally, we don't like it when Core / Blockstream attempts to steal functionality away from nodes while using misleading terminology - as u/chinawat has repeatedly been pointing out lately.
We know a messy, dangerous, centrally planned hack when we see it - and SegWit is a messy, dangerous, centrally planned hack.
If Core/Blockstream attempts to foce messy and dangerous code like SegWit-as-a-soft-fork on the community, we can and should and we will reject SegWit - to protect our billions of dollars of investment in Bitcoin (which could turn into trillions of dollars someday - if we continue to protect our code from poison pills and trojans like SegWit).
Too bad you lost my support (and the support of many, many other Bitcoin users), Core / Blockstream! But it's your own fault for releasing shitty code.
Below are some earlier comments from me showing how I quickly turned from one of the most outspoken supporters of Segwit (in that single OP I wrote the day I saw Pieter Wuille's presentation on YouTube) - into one of most outspoken opponents of SegWit:
I also think Pieter Wuille is a great programmer and I was one of the first people to support SegWit after it was announced at a congress a few months ago.
But then Blockstream went and distorted SegWit to fit it into their corporate interests (maintaining their position as the dominant centralized dev team - which requires avoiding hard-forks). And Blockstream's corporate interests don't always align with Bitcoin's interests.
https://np.reddit.com/btc/comments/57zbkp/if_blockstream_were_truly_conservative_and_wanted/
As noted in the link in the section title above, I myself was an outspoken supporter championing SegWit on the day when I first the YouTube of Pieter Wuille explaining it at one of the early "Scaling Bitcoin" conferences.
Then I found out that doing it as a soft fork would add unnecessary "spaghetti code" - and I became one of the most outspoken opponents of SegWit.
https://np.reddit.com/btc/comments/5ejmin/coreblockstream_is_living_in_a_fantasy_world_in/
Pieter Wuille's SegWit would be a great refactoring and clean-up of the code (if we don't let Luke-Jr poison it by packaging it as a soft-fork)
https://np.reddit.com/btc/comments/4kxtq4/i_think_the_berlin_wall_principle_will_end_up/
Probably the only prominent Core/Blockstream dev who does understand this kind of stuff like the Robustness Principle or its equivalent reformulation in terms of covariant and contravariant types is someone like Pieter Wuille – since he’s a guy who’s done a lot of work in functional languages like Haskell – instead of being a myopic C-tard like most of the rest of the Core/Blockstream devs. He’s a smart guy, and his work on SegWit is really important stuff (but too bad that, yet again, it’s being misdelivered as a “soft-fork,” again due to the cluelessness of someone like Luke-Jr, whose grasp of syntax and semantics – not to mention society – is so glaringly lacking that he should have been recognized for the toxic influence that he is and shunned long ago).
https://np.reddit.com/btc/comments/4k6tke/the_tragedy_of/
The damage which would be caused by SegWit (at the financial, software, and governance level) would be massive:
  • Millions of lines of other Bitcoin code would have to be rewritten (in wallets, on exchanges, at businesses) in order to become compatible with all the messy non-standard kludges and workarounds which Blockstream was forced into adding to the code (the famous "technical debt") in order to get SegWit to work as a soft fork.
  • SegWit was originally sold to us as a "code clean-up". Heck, even I intially fell for it when I saw an early presentation by Pieter Wuille on YouTube from one of Blockstream's many, censored Bitcoin scaling stalling conferences)
  • But as we all later all discovered, SegWit is just a messy hack.
  • Probably the most dangerous aspect of SegWit is that it changes all transactions into "ANYONE-CAN-SPEND" without SegWit - all because of the messy workarounds necessary to do SegWit as a soft-fork. The kludges and workarounds involving SegWit's "ANYONE-CAN-SPEND" semantics would only work as long as SegWit is still installed.
  • This means that it would be impossible to roll-back SegWit - because all SegWit transactions that get recorded on the blockchain would now be interpreted as "ANYONE-CAN-SPEND" - so, SegWit's dangerous and messy "kludges and workarounds and hacks" would have to be made permanent - otherwise, anyone could spend those "ANYONE-CAN-SPEND" SegWit coins!
Segwit cannot be rolled back because to non-upgraded clients, ANYONE can spend Segwit txn outputs. If Segwit is rolled back, all funds locked in Segwit outputs can be taken by anyone. As more funds gets locked up in segwit outputs, incentive for miners to collude to claim them grows.
https://np.reddit.com/btc/comments/5ge1ks/segwit_cannot_be_rolled_back_because_to/
https://np.reddit.com/btc/search?q=segwit+anyone+can+spend&restrict_sr=on&sort=relevance&t=all
https://np.reddit.com/btc/comments/5r9cu7/the_real_question_is_how_fast_do_bugs_get_fixed/
Why are more and more people (including me!) rejecting SegWit?
(1) SegWit is the most radical and irresponsible change ever proposed for Bitcoin:
"SegWit encumbers Bitcoin with irreversible technical debt. Miners should reject SWSF. SW is the most radical and irresponsible protocol upgrade Bitcoin has faced in its history. The scale of the code changes are far from trivial - nearly every part of the codebase is affected by SW" Jaqen Hash’ghar
https://np.reddit.com/btc/comments/5rdl1j/segwit_encumbers_bitcoin_with_irreversible/
3 excellent articles highlighting some of the major problems with SegWit: (1) "Core Segwit – Thinking of upgrading? You need to read this!" by WallStreetTechnologist (2) "SegWit is not great" by Deadalnix (3) "How Software Gets Bloated: From Telephony to Bitcoin" by Emin Gün Sirer
https://np.reddit.com/btc/comments/5rfh4i/3_excellent_articles_highlighting_some_of_the/
"The scaling argument was ridiculous at first, and now it's sinister. Core wants to take transactions away from miners to give to their banking buddies - crippling Bitcoin to only be able to do settlements. They are destroying Satoshi's vision. SegwitCoin is Bankcoin, not Bitcoin" ~ u/ZeroFucksG1v3n
https://np.reddit.com/btc/comments/5rbug3/the_scaling_argument_was_ridiculous_at_first_and/
u/Uptrenda on SegWit: "Core is forcing every Bitcoin startup to abandon their entire code base for a Rube Goldberg machine making their products so slow, inconvenient, and confusing that even if they do manage to 'migrate' to this cluster-fuck of technical debt it will kill their businesses anyway."
https://np.reddit.com/btc/comments/5e86fg/uuptrenda_on_segwit_core_is_forcing_every_bitcoin/
"SegWit [would] bring unnecessary complexity to the bitcoin blockchain. Huge changes it introduces into the client are a veritable minefield of issues, [with] huge changes needed for all wallets, exchanges, remittance, and virtually all bitcoin software that will use it." ~ u/Bitcoinopoly
https://np.reddit.com/btc/comments/5jqgpz/segwit_would_bring_unnecessary_complexity_to_the/
Just because something is a "soft fork" doesn't mean it isn't a massive change. SegWit is an alt-coin. It would introduce radical and unpredictable changes in Bitcoin's economic parameters and incentives. Just read this thread. Nobody has any idea how the mainnet will react to SegWit in real life.
https://np.reddit.com/btc/comments/5fc1ii/just_because_something_is_a_soft_fork_doesnt_mean/
Core/Blockstream & their supporters keep saying that "SegWit has been tested". But this is false. Other software used by miners, exchanges, Bitcoin hardware manufacturers, non-Core software developers/companies, and Bitcoin enthusiasts would all need to be rewritten, to be compatible with SegWit
https://np.reddit.com/btc/comments/5dlyz7/coreblockstream_their_supporters_keep_saying_that/
SegWit-as-a-softfork is a hack. Flexible-Transactions-as-a-hard-fork is simpler, safer and more future-proof than SegWit-as-a-soft-fork - trivially solving malleability, while adding a "tag-based" binary data format (like JSON, XML or HTML) for easier, safer future upgrades with less technical debt
https://np.reddit.com/btc/comments/5a7husegwitasasoftfork_is_a_hack/
(2) Better solutions than SegWit are now available (Bitcoin Unlimited, FlexTrans):
ViABTC: "Why I support BU: We should give the question of block size to the free market to decide. It will naturally adjust to ever-improving network & technological constraints. Bitcoin Unlimited guarantees that block size will follow what the Bitcoin network is capable of handling safely."
https://np.reddit.com/btc/comments/574g5l/viabtc_why_i_support_bu_we_should_give_the/
"Why is Flexible Transactions more future-proof than SegWit?" by u/ThomasZander
https://np.reddit.com/btc/comments/5rbv1j/why_is_flexible_transactions_more_futureproof/
Bitcoin's specification (eg: Excess Blocksize (EB) & Acceptance Depth (AD), configurable via Bitcoin Unlimited) can, should & always WILL be decided by ALL the miners & users - not by a single FIAT-FUNDED, CENSORSHIP-SUPPORTED dev team (Core/Blockstream) & miner (BitFury) pushing SegWit 1.7MB blocks
https://np.reddit.com/btc/comments/5u1r2d/bitcoins_specification_eg_excess_blocksize_eb/
The Blockstream/SegWit/LN fork will be worth LESS: SegWit uses 4MB storage/bandwidth to provide a one-time bump to 1.7MB blocksize; messy, less-safe as softfork; LN=vaporware. The BU fork will be worth MORE: single clean safe hardfork solving blocksize forever; on-chain; fix malleability separately.
https://np.reddit.com/btc/comments/57zjnk/the_blockstreamsegwitln_fork_will_be_worth_less/
(3) Very few miners actually support SegWit. In fact, over half of SegWit signaling comes from just two fiat-funded miners associated with Core / Blockstream: BitFury and BTCC:
Brock Pierce's BLOCKCHAIN CAPITAL is part-owner of Bitcoin's biggest, private, fiat-funded private dev team (Blockstream) & biggest, private, fiat-funded private mining operation (BitFury). Both are pushing SegWit - with its "centrally planned blocksize" & dangerous "anyone-can-spend kludge".
https://np.reddit.com/btc/comments/5sndsz/brock_pierces_blockchain_capital_is_partowner_of/
(4) Hard forks are simpler and safer than soft forks. Hard forks preserve your "right to vote" - so Core / Blockstream is afraid of hard forks a/k/a "full node refendums" - because they know their code would be rejected:
The real reason why Core / Blockstream always favors soft-forks over hard-forks (even though hard-forks are actually safer because hard-forks are explicit) is because soft-forks allow the "incumbent" code to quietly remain incumbent forever (and in this case, the "incumbent" code is Core)
https://np.reddit.com/btc/comments/4080mw/the_real_reason_why_core_blockstream_always/
Reminder: Previous posts showing that Blockstream's opposition to hard-forks is dangerous, obstructionist, selfish FUD. As many of us already know, the reason that Blockstream is against hard forks is simple: Hard forks are good for Bitcoin, but bad for the private company Blockstream.
https://np.reddit.com/btc/comments/4ttmk3/reminder_previous_posts_showing_that_blockstreams/
"They [Core/Blockstream] fear a hard fork will remove them from their dominant position." ... "Hard forks are 'dangerous' because they put the market in charge, and the market might vote against '[the] experts' [at Core/Blockstream]" - ForkiusMaximus
https://np.reddit.com/btc/comments/43h4cq/they_coreblockstream_fear_a_hard_fork_will_remove/
The proper terminology for a "hard fork" should be a "FULL NODE REFERENDUM" - an open, transparent EXPLICIT process where everyone has the right to vote FOR or AGAINST an upgrade. The proper terminology for a "soft fork" should be a "SNEAKY TROJAN HORSE" - because IT TAKES AWAY YOUR RIGHT TO VOTE.
https://np.reddit.com/btc/comments/5e4e7d/the_proper_terminology_for_a_hard_fork_should_be/
If Blockstream were truly "conservative" and wanted to "protect Bitcoin" then they would deploy SegWit AS A HARD FORK. Insisting on deploying SegWit as a soft fork (overly complicated so more dangerous for Bitcoin) exposes that they are LYING about being "conservative" and "protecting Bitcoin".
https://np.reddit.com/btc/comments/57zbkp/if_blockstream_were_truly_conservative_and_wanted/
"We had our arms twisted to accept 2MB hardfork + SegWit. We then got a bait and switch 1MB + SegWit with no hardfork, and accounting tricks to make P2SH transactions cheaper (for sidechains and Lightning, which is all Blockstream wants because they can use it to control Bitcoin)." ~ u/URGOVERNMENT
https://np.reddit.com/btc/comments/5ju5r8/we_had_our_arms_twisted_to_accept_2mb_hardfork/
u/Luke-Jr invented SegWit's dangerous "anyone-can-spend" soft-fork kludge. Now he helped kill Bitcoin trading at Circle. He thinks Bitcoin should only hard-fork TO DEAL WITH QUANTUM COMPUTING. Luke-Jr will continue to kill Bitcoin if we continue to let him. To prosper, BITCOIN MUST IGNORE LUKE-JR.
https://np.reddit.com/btc/comments/5h0yf0/ulukejr_invented_segwits_dangerous_anyonecanspend/
Normal users understand that SegWit-as-a-softfork is dangerous, because it deceives non-upgraded nodes into thinking transactions are valid when actually they're not - turning those nodes into "zombie nodes". Greg Maxwell and Blockstream are jeopardizing Bitcoin - in order to stay in power.
https://np.reddit.com/btc/comments/4mnpxx/normal_users_understand_that_segwitasasoftfork_is/
"Negotiations have failed. BS/Core will never HF - except to fire the miners and create an altcoin. Malleability & quadratic verification time should be fixed - but not via SWSF political/economic trojan horse. CHANGES TO BITCOIN ECONOMICS MUST BE THRU FULL NODE REFERENDUM OF A HF." ~ u/TunaMelt
https://np.reddit.com/btc/comments/5e410j/negotiations_have_failed_bscore_will_never_hf/
"Anything controversial ... is the perfect time for a hard fork. ... Hard forks are the market speaking. Soft forks on any issues where there is controversy are an attempt to smother the market in its sleep. Core's approach is fundamentally anti-market" ~ u/ForkiusMaximus
https://np.reddit.com/btc/comments/5f4zaa/anything_controversial_is_the_perfect_time_for_a/
As Core / Blockstream collapses and Classic gains momentum, the CEO of Blockstream, Austin Hill, gets caught spreading FUD about the safety of "hard forks", falsely claiming that: "A hard-fork forced-upgrade flag day ... disenfranchises everyone who doesn't upgrade ... causes them to lose funds"
https://np.reddit.com/btc/comments/41c8n5/as_core_blockstream_collapses_and_classic_gains/
Core/Blockstream is living in a fantasy world. In the real world everyone knows (1) our hardware can support 4-8 MB (even with the Great Firewall), and (2) hard forks are cleaner than soft forks. Core/Blockstream refuses to offer either of these things. Other implementations (eg: BU) can offer both.
https://np.reddit.com/btc/comments/5ejmin/coreblockstream_is_living_in_a_fantasy_world_in/
Blockstream is "just another shitty startup. A 30-second review of their business plan makes it obvious that LN was never going to happen. Due to elasticity of demand, users either go to another coin, or don't use crypto at all. There is no demand for degraded 'off-chain' services." ~ u/jeanduluoz
https://np.reddit.com/btc/comments/59hcvblockstream_is_just_another_shitty_startup_a/
(5) Core / Blockstream's latest propaganda "talking point" proclaims that "SegWit is a blocksize increase". But we don't want "a" random, arbitrary centrally planned blocksize increase (to a tiny 1.7MB) - we want _market-based blocksizes - now and into the future:_
The debate is not "SHOULD THE BLOCKSIZE BE 1MB VERSUS 1.7MB?". The debate is: "WHO SHOULD DECIDE THE BLOCKSIZE?" (1) Should an obsolete temporary anti-spam hack freeze blocks at 1MB? (2) Should a centralized dev team soft-fork the blocksize to 1.7MB? (3) OR SHOULD THE MARKET DECIDE THE BLOCKSIZE?
https://np.reddit.com/btc/comments/5pcpec/the_debate_is_not_should_the_blocksize_be_1mb/
The Bitcoin community is talking. Why isn't Core/Blockstream listening? "Yes, [SegWit] increases the blocksize but BU wants a literal blocksize increase." ~ u/lurker_derp ... "It's pretty clear that they [BU-ers] want Bitcoin, not a BTC fork, to have a bigger blocksize." ~ u/WellSpentTime
https://np.reddit.com/btc/comments/5fjh6l/the_bitcoin_community_is_talking_why_isnt/
"The MAJORITY of the community sentiment (be it miners or users / hodlers) is in favour of the manner in which BU handles the scaling conundrum (only a conundrum due to the junta at Core) and SegWit as a hard and not a soft fork." ~ u/pekatete
https://np.reddit.com/btc/comments/593voi/the_majority_of_the_community_sentiment_be_it/
(6) Core / Blockstream want to radically change Bitcoin to centrally planned 1.7MB blocksize, and dangerous "anyone-can-spend" semantics. The market wants to go to the moon - with Bitcoin's original security model, and Bitcoin's original market-based (miner-decided) blocksize.
Bitcoin Unlimited is the real Bitcoin, in line with Satoshi's vision. Meanwhile, BlockstreamCoin+RBF+SegWitAsASoftFork+LightningCentralizedHub-OfflineIOUCoin is some kind of weird unrecognizable double-spendable non-consensus-driven fiat-financed offline centralized settlement-only non-P2P "altcoin"
https://np.reddit.com/btc/comments/57brcb/bitcoin_unlimited_is_the_real_bitcoin_in_line/
The number of blocks being mined by Bitcoin Unlimited is now getting very close to surpassing the number of blocks being mined by SegWit! More and more people are supporting BU's MARKET-BASED BLOCKSIZE - because BU avoids needless transaction delays and ultimately increases Bitcoin adoption & price!
https://np.reddit.com/btc/comments/5rdhzh/the_number_of_blocks_being_mined_by_bitcoin/
I have just been banned for from /Bitcoin for posting evidence that there is a moderate/strong inverse correlation between the amount of Bitcoin Core Blocks mined and the Bitcoin Price (meaning that as Core loses market share, Price goes up).
https://np.reddit.com/btc/comments/5v10zw/i_have_just_been_banned_for_from_rbitcoin_fo
Flipping the Script: It is Core who is proposing a change to Bitcoin, and BU/Classic that is maintaining the status quo.
https://np.reddit.com/btc/comments/5v36jy/flipping_the_script_it_is_core_who_is_proposing_a/
The main difference between Bitcoin core and BU client is BU developers dont bundle their economic and political opinions with their code
https://np.reddit.com/btc/comments/5v3rt2/the_main_difference_between_bitcoin_core_and_bu/
TL;DR:
You wanted people like me to support you and install your code, Core / Blockstream?
Then you shouldn't have a released messy, dangerous, centrally planned hack like SegWit-as-a-soft-fork - with its random, arbitrary, centrally planned, ridiculously tiny 1.7MB blocksize - and its dangerous "anyone-can-spend" soft-fork semantics.
Now it's too late. The market will reject SegWit - and it's all Core / Blockstream's fault.
The market prefers simpler, safer, future-proof, market-based solutions such as Bitcoin Unlimited.
submitted by ydtm to btc [link] [comments]

Core/Blockstream are now in the Kübler-Ross "Bargaining" phase - talking about "compromise". Sorry, but markets don't do "compromise". Markets do COMPETITION. Markets do winner-takes-all. The whitepaper doesn't talk about "compromise" - it says that 51% of the hashpower determines WHAT IS BITCOIN.

They've finally entered the Kübler-Ross "bargaining" phase - now they're begging for some kind of "compromise".
But actually, markets aren't about compromise. Markets are about competition. Markets are about winner-takes-all.
And the Bitcoin whitepaper never mentions anything about "compromise".
It simply says that 51% of the hashpower determines what is Bitcoin.
And as we know - the best coin will win.
Which will probably be Bitcoin Unlimited with its market-based blocksizes - and not SegWit with its 1.7MB centrally planned blocksize based on a dangerous anyone-can-spend spaghetti-code soft-fork.
Let's review how this played out:
And lo and behold, Core/Blockstream's reliance on fiat funding and central planning and censorship has culminated in this pathetic piece of shit called SegWit, with the following worthless "features" that nobody even wants:
No wonder the only two miners who are supporting this pathetic piece of shit called SegWit are Blockstream's two buddies BitFury and BTCC - who are (surprise! surprise!) also funded by the same corrupt fiat-financed central bankers who fund Blockstream itself.
Market-based solutions from independent devs are better than censorship-based non-solutions from devs getting paid by central bankers
So eventually, a couple of market-based, non-fiat-funded dev teams produced Bitcoin Unlimited and Bitcoin Classic.
And (surprise! surprise!) these two market-based, non-fiat-funded dev teams produced much better technology and economics - based on the original principles of Satoshi's Bitcoin:
By listening to real people in the actual market, and by following Satoshi's principles as stated in the whitepaper, Bitcoin Unlimited has been able to (surprise! surprise!) offer what real people in the actual market actually want - which is currently:
FlexTrans is much better than SegWit
Also, these independent, non-fiat-financed devs developed Flexible Transactions, which is way better than SegWit.
Flexible Transactions can easily fix malleability and quadratic hashing - while also introducing a simple, easy-to-use, future-proof tag-based format similar to JSON or HTML permitting future upgrades without the need for a hard fork.
So Flexible Transactions provides the same things as SegWit - without the dangerous mess of SegWit's "anyone-can-spend" soft-fork hack - which Core/Blockstream tried to force on everyone - because they want to take away our right to vote via a hard fork - because they know that if we actually had a hard fork a/k/a full node referendum, everyone would vote against Core/Blockstream.
The market wants to decide the blocksize
So more and more of the smart, non-Blockstream-aligned miners, starting with ViaBTC and now including many others, have been adopting Bitcoin Unlimited - because they understand that:
  • Market-based blocksizes are the right, consensus-based mechanism to provide simple and safe on-chain scaling to solve the urgent problems of transaction delays and network congestion - now and in the future
  • Every increase in the blocksize roughly corresponds to the same increase squared in terms of price
  • ie 2x bigger blocks will lead to 4x higher price, 3x bigger blocks will correspond with 9x higher price, etc. - which means that bigger blocks will make everyone happy: more profits for miners, and no more high fees or transaction delays for users.
Now Core/Blockstream are starting to bitch and moan and beg about "compromise"
And actually, we couldn't answer "Sorry it's too late for compromise" even if we wanted to.
Because markets and economics and cryptocurrencies aren't about compromises.
Markets are about competition - they're about winner-takes-all.
Nakamoto Consensus is about 51% of the hashpower decides what the rules are.
Imagine if Yahoo Email were to suddenly start begging with Google Mail for "compromise". What would that even mean in the first place??
Yahoo wrote crappy email code - based on their crappy corporate culture - so the market abandoned their crappy (and buggy and insecure) email service.
Core/Blockstream is similar in some ways to Yahoo. They wrote crappy code - because they have a crappy "corporate culture" - because they accept millions of dollars in fiat from central bankers at places like AXA - and because they accept censorship on shit-forums like r\bitcoin - which is why they have no clue about the real needs of real people in the real market in the real world.
Censorship and fiat made Core/Blockstream fragile and out-of-touch
Core/Blockstream devs enjoy the "luxury" of being able to put their head in the sand and hide from the reality of the "shreaking" masses of actual people actually trying to use Bitcoin, because:
  • They get millions of dollars in fiat shoveled to them by central bankers,
  • They conduct their "debates" in the fantasy-land of the shit-forum r\bitcoin where all the important comments get deleted and all the intelligent posters got banned long ago - including quotes from Satoshi.
And then (surprise! surprise!) the following happened:
But in a decentralized, permissionless, open-source system like Bitcoin, there is not a single thing that CEO Adam Back u/adam3us and CTO Greg Maxwell u/nullc at their shitty little AXA-funded startup Blockstream or u/theymos and u/bashco on their shitty little censored forum r\bitcoin can do to stop Bitcoin Unlimited from taking over the network - because in open-source and in economics and in markets, the best code and the best cryptocurrency wins.
Everyone (except Core/Blockstream) predicted this would happen
So now - predictably - the Core/Blockstream devs and their low-information supporters are all running around saying "Nobody could have predicted this!"
But actually everyone has been shouting at the top of their lungs predicting this for years - including the most important old-time Bitcoin devs supporting on-chain scaling like Mike Hearn, Gavin Andresen and Jeff Garzik who were all "censored, hounded, DDoS'd, attacked, slandered & removed" - plus new-time devs like Peter Rizun u/Peter__R who provided major scaling innovations like XThin - by the vicious drooling toxic authoritarian goons involved with Core/Blockstream.
Everyone has been predicting the current delays and congestion and high fees for years, out here in the reality of the marketplace, in the reality of the uncensored forums - away from Core/Blockstream's centralized back-room closed-door fiat-funded censorship-supported PowerPoint presentations in Hong Kong and Silicon Valley, away from years and years of Core/Blockstream's all-talk-no-action scaling stalling conferences.
The Honey Badger of Bitcoin doesn't give a fuck about "compromise" and "censorship" and "central planning".
The Honey Badger of Bitcoin doesn't give a fuck about yet-another centrally planned blocksize (Now with 1.7MB! SegWit is scaling!TM) which some economically ignorant fiat-funded dev team happened to pull out of their ass and bundle into a radical and irresponsible spaghetti-code SegWit soft-fork.
Markets aren't about "compromise". Markets are about competition.
As u/ForkiusMaximus recently pointed out: The market couldn't even give a fuck if it wanted to - because markets and cryptocurrencies are not about the politics of "compromise" - they're about the economics of competition.
Markets are about decentralization, and they're about Nakamoto Consensus, where 51% of the hashpower decides the rules and everyone else either gets on the bandwagon or withers away watching their hashpower and coin price sink into oblivion.
So, anyone who even brings up the topic of "compromise" is simply showing that they have a fundamental misunderstanding of how markets work, and how Nakamoto Consensus works.
This actually isn't very surprising. Blockstream CEO Adam Back u/adam3us and Blockstream CTO Greg Maxwell u/nullc and all the rest of the so-called "Core devs" and all their low-information hangers-on like the economic idiot Blockstream founder Mark Friedenbach u/maaku7 have never really understood Bitcoin or markets.
And that's fine and normal. Plenty of individuals don't understand markets very well. But such people simply lose their own money - and they generally don't get put in charge of losing $20 billion of other people's money.
Markets don't need managers or central planners.
Markets run very well on their own - and they don't like central planning or censorship.
Now Core/Blockstream has finally entered the Kübler-Ross "bargaining" phase
So now some people at Core/Blockstream and some of their low-information supporters have have started bitching and moaning and whining about "compromise", as they sink into the Kübler-Ross "bargaining" phase - while their plans are all in shambles, and they've failed in their attempts to hijack our network and our currency.
Meanwhile, the Honey Badger of Bitcoin doesn't give a fuck about a bunch of central planners and censors whining about "compromise".
Bitcoin Unlimited just keeps stealing more and more hashpower away from Core - until the day comes when we decide to fork their ass into the garbage heap of shitty, failed alt-coins.
Fuck Blockstream/Core and the central bankers and censors they rode in on
We told them for years that they were only shooting themselves in the foot with their closed-door back-room fiat-financed wheeling and dealing and their massive censorship.
We told them they were only giving themselves enough rope to hang themselves with.
Now that it's actually happening, we couldn't say "it's too late for compromise" even if we wanted to - because there is no such thing as "compromise" in markets or cryptocurrencies.
Markets are all about competition
And Bitcoin is all about 51% of the hashpower.
  • Bitcoin Core decided to bet on hard-coded centrally planned 1.7MB blocksize based on a a shitty spaghetti-code soft-fork. That's their choice. They made their bed now let them lie in it.
  • Meanwhile, Bitcoin Unlimited decided to bet on market-based blocksizes. And that's the market's choice. Bitcoin Unlimited listened to the market - and (suprise! surprise!) that's why more and more hashpower is now mining Bitcoin Unlimited blocks.
Ladies and Gentlemen, start your engines Bitcoin Unlimited nodes.
And may the best coin win.
submitted by ydtm to btc [link] [comments]

ShionCoin Console Basics

The following is a brief overview of the commands provided by the "shc" utility console program.
The utility program "shc" communication with the server (shcoind) are restricted to the local host that the service is running. You must use the stratum API in order to access the server from a remote machine.
A sub-set of all the commands are provided here. This guide attempts to concentrate on commonly used commands that are useful. Run "shc help" for a full list of commands. Run "shc help " for details about running that particular command.
You can enter an interactive mode by running "shc --prompt".
Run the daemon with "shcoind --debug" in order to print additional information to the log file (on linux, "/valib/share/shcoind.log") for diagnostic purposes.
ShionCoin "pub-key" coin addresses typically starts with "S" or "R". A "script address" will start with "1" and a seg-wit address will start with "3". Coin addresses are verified when entered on the command-line in order to ensure that the address is prudent in respect to the coin interface.
All fees for extended transactions, such as creating context and aliases, are either stored (for update purposes) in a local extended account and/or are provided as mining fees. You can use the "wallet.donate" command to intentionally create a transaction which includes a specified mining reward value.

Wallet Commands

The wallet commands provides capabilities to transfer funds and manage accounts. Each account can contain several coin addresses and has a counter-part "extended account" that is not visible.
Wallet Info: wallet.info
Display statistical and runtime information on wallet operations.
shc wallet.info { "version": 3010000, "walletversion": 60000, "balance": 658, "keypoololdest": 1517000561, "keypoolsize": 101 }
Create Coin Address: wallet.new
The "wallet.new" command is used to create a normal (non seg-wit) coin address and associate it with an account name. Coin addresses may be automatically generated for accounts, for example in order to return "change" in a fund transfer transaction. All change is directly returned to the associated account.
shc wallet.new test S2fzfzf1SStvaMzjGpCtYKxY3t8PXus9Ci
List Accounts: wallet.list
The "wallet.list" command provides a balance of all accounts in the coin wallet.
shc wallet.list { "": 0, "bank": 658, "system": 0 }
Three accounts are created by default. The "" account receives coinbase rewards which are then distributed to users based on their stratum stats. The "bank" account is a 0.1% cut of the rewards received from the stratum mining pool. The "system" account is currently reserved for a cpu-miner which attempts a single mining operation each time new task work is assigned to miners. The frequency of how often this occurs is based on tracking the "luck" of past attempts.
List Coin Addresses: wallet.listaddr
The "wallet.listaddr" command will list all of the coin addresses associated with an account.
shc wallet.listaddr test ["S2fzfzf1SStvaMzjGpCtYKxY3t8PXus9Ci"]
Create Transaction: wallet.send
The "wallet.send" command is the primary method of sending funds.
All ShionCoin transactions are sent with at least the 0.0001 SHC minimum fee. Providing the minimum fee is provided, any fee can is permitted and affects the priority of the transaction.
shc wallet.send bank S2fzfzf1SStvaMzjGpCtYKxY3t8PXus9Ci 10 307711dace8c0583b744af8acd1df2073e36b0c7a54b8830a15ae146f8c22ddb
Test Create Transaction: wallet.tsend
You can "test send" a transaction in order to determine the aproximate fee and size that would result.
shc wallet.tsend bank SLbnKamvSx8FhaBNpHUwffFDLZ16J8phdX 10 { "amount": 10, "tx-amount": 98.999900, "size": 300, "virt-size": 226, "fee": 0.000100, "inputs": 1, "priority": 1085539000000 }
Create Batch Transaction(s): wallet.bsend
The "wallet.bsend" command allows you to transfer funds that are more complicated than would be permitted in a single transaction. Multiple transactions will be created, as neccessary, in order to send the specified coin value. The total value commited to be sent may be lower than the value requested under certain circumstances.
Create Certified Transaction: wallet.csend
The "wallet.csend" associated a pre-created certificate with the coin transfer. The certificate may be used to associate with the certificate, or provide a method to identity the source of the funds.
shc wallet.csend bank SLbnKamvSx8FhaBNpHUwffFDLZ16J8phdX 10
Create Stamp Transaction: wallet.stamp
The "wallet.stamp" command allows you to create a short message (up to 135 characters), or reference a geodetic location, to associate with a local coin address. The stamp transaction is the exclusive method of claiming spring matix location coins. Creating a stamp in the format "geo:," will result in a single SHC coin, once processed on the network, being rewarded for all locations not yet discovered in the spring matrix. A minimum transaction fee (0.0001) is applied for each stamp transaction created.
Use the "ctx.findloc" command in order to search for locations active in the sprint matrix.
Validate Address: wallet.donate
Donated coins are added to the upcoming block reward. Donations may be optionally associated with a certificate. The maximum donation value in a single transaction is 500 coins. Donations are associated with the coin address that generates them, and may contain a geodetic stamp depending on configuration and availability.
The total cost will include the donation coin value specified plus a minimum transaction fee (0.0001 SHC).
{ "version": 1, "flag": 1025, "txid": "ace04609d0eca593b73a3f1afb1dcfeb10049c4ab4098ff9b17e01da65bf2ec6", .. "ident": { "version": 3, "expire": " ", "geo": "46.770000,113.980000", "addr": "SFrXpo9ykcSeycTdMaFu3xWwJFxN5gkUH4" } }
Validate Address: wallet.validate
The "wallet.validate" command returns general information about the coin address specified, including whether the coin address is contained in the local wallet.
shc wallet.validate SLbnKamvSx8FhaBNpHUwffFDLZ16J8phdX { "isvalid": true, "address": "SLbnKamvSx8FhaBNpHUwffFDLZ16J8phdX", "ismine": true, "account": "system" }
Validate Address: wallet.key
Obtain a code that identifies the private key of a coin address.
Validate Address: wallet.setkey
Create a new coin address, for the specified account, with a private key code.
Validate Address: wallet.keyphrase
Obtain a set of phrases that identify the private key associated with a coin address.
Validate Address: wallet.setkeyphrase
Create a coin address in the wallet given a key phrase.
Export Wallet (json): wallet.export
Creates a JSON formatted backup of all the accounts managed.
Export Wallet (datafile): wallet.exportdat
Creates a binary backup, in the tradition bitcoin wallet format, of all the accounts in the wallet.
Import Wallet (json): wallet.import
Creates a JSON formatted backup of all the accounts managed.
Scan Wallet: wallet.rescan
Cycle through all known wallet transactions and verify their state in the block-chain.

Block Commands

BlockChain Info: block.info
Print summarized information about the block-chain.
shc block.info { "version": 2000000, "blockversion": 2, "walletversion": 60000, "blocks": 77029, "difficulty": 0.000488, "pooledtx": 0, "currentblockhash": "5c4e3a637d857c7df925dda1c017dd3864c0fb95c1421276619810f5b95fc8c5", "errors": "" }
Print Block (hash): block.get
Print detailed information about the specified block hash.
shc block.get bc157eefd48e18152c70ad2937bd44e6bb38d218bf13c262a844a3d0ae9264d6 { "blockhash": "bc157eefd48e18152c70ad2937bd44e6bb38d218bf13c262a844a3d0ae9264d6", "version": 536870912, "merkleroot": "5bda555d945bc36806f1eb4913a47a2ecad4569133cce1d59bd82ad94e7be1c6", "time": 1521898215, "stamp": "03/24/18 07:30:15", "nonce": 4422421, "bits": "1e07ffff", "previousblockhash": "3312abddb29aea55f44a0e3c52d397d3041b9e2deaa160f2ac415cdca05057b9", .. }
Print Block Hash (height): block.hash
Obtain the block hash for a specified block height.
shc block.hash 77022 bc157eefd48e18152c70ad2937bd44e6bb38d218bf13c262a844a3d0ae9264d6
Export BlockChain: block.export
Export an entire block-chain to a binary file. The actual export of data is performed asynchronously (in the background), and the log file should be reviewed to determine when the operation is actually done.
shc block.export /root/.shc/block.bin { "mode": "export-block", "minheight": 0, "maxheight": 0, "path": "/root/.shc/block.bin", "state": "init" }
tail /valog/share/shcoind.log ..
[03/24/18 07:47:14] info: shc: PerformBlockChainOperation: saved 77105 blocks to path "/root/.shc/block.bin".
Import BlockChain: block.import
Import a previously exported block-chain into the live system. The imported file will only over-write block records that do not previously exist.
BlockChain Scan: block.verify
Perform an integrity check against the last X blocks in the block-chain.

Transaction Commands

Print Transaction: tx.get
Print details for a particular transaction from it's transaction hash.
shc tx.get 307711dace8c0583b744af8acd1df2073e36b0c7a54b8830a15ae146f8c22ddb { "version": 1, "flag": 1, "txid": "307711dace8c0583b744af8acd1df2073e36b0c7a54b8830a15ae146f8c22ddb", .. }
Print Transaction: tx.pool
Print details for all transaction currently pending in the active "mempool" queue. These are transactions that are actively being inserted into mined blocks.
Print Transaction: tx.validate
Validate a transaction hash associated with the local wallet. Prints summarized information about all local coin addresses associated with the transaction.
shc tx.validate 307711dace8c0583b744af8acd1df2073e36b0c7a54b8830a15ae146f8c22ddb [{ "spent": "false", "ismine": "true", "address": "S7viXBKwUZKy4aPCby3oXzWFDxhZKjGipA" }, { "spent": "false", "ismine": "true", "address": "S2fzfzf1SStvaMzjGpCtYKxY3t8PXus9Ci" }]

Peer Commands

Import Peers: peer.info
Display a summary of information relating to connected peers.
{ "clientversion": 3010000, "protocolversion": 2000000, "socketport": 24104, "connections": 3, "networkhashps": 11609, "errors": "" }
Import Peers: peer.list
Display information about each node peer currently connected to the coin interface.
Export Peers: peer.export
Export all of the known peers to a JSON file.
shc peer.export /root/.shc/peer.json { "mode": "peer.export", "path": "/root/.shc/peer.json", "state": "finished" }
Import Peers: peer.add
Import a JSON file containing node peer information.
Remove Peer: peer.remove
Disconnect and remove the specified peer from the system.

Context Commands

Context Info: ctx.info
Print the current fee to create a context transaction and the total number of context records in the system.
{ "fee": 25, "total": 1 }
Print String Context: ctx.getstr
Prints the ASCII value associated with a particular context name.
shc ctx.getstr "test name" test value
Print Context: ctx.get
Prints detailed information about a context record given it's context hash.
shc ctx.get ab5b128ce3674f81f0271efbbbb191fed56e9a80 { "version": 3, "label": "ab5b128ce3674f81f0271efbbbb191fed56e9a80 test name (1zgfTHd5BQA)", "expire": "Mar 23 08:28:39 2020", "flags": 10244, "signature": "e0539d3ecb54c5c0a29ccd69f0b03dfdfb58bc24", "hash": "ab5b128ce3674f81f0271efbbbb191fed56e9a80", "valuesize": 10, "valuecrc": "1zgfTHd5BQA", "tx": "0dbf21191091e33ad7be3b1ce1983ffffdbedeb804e3ce934021f0fad038d50e" }
Create String Context: ctx.findloc
Search for a location by it's name or with geodetic cordinates.
The "ctx.findloc" will scan an area and attempt to find a location within it. This area includes a span of about 100 sq. miles. The closest location with the smallest precision found will be returned. In addition, geodetic information provided by the share library is also utilized.
shc ctx.findloc "geo:46.9,114.2" { "name": "missoula, mt", "summary": "Montana", "zone": "America/Denver", "code": "MUNI", "country": "US", "geo": "46.94000,114.04000", "type": "Municipal Zone", "springable": "false" } shc ctx.findloc "Missoula, MT" { "name": "missoula, mt", "summary": "Montana", "zone": "America/Denver", "code": "MUNI", "country": "US", "geo": "46.94000,114.04000", "type": "Municipal Zone", "springable": "false" }
Note: The "springable" value denotes whether the geodetic location can be claimed in the SHC spring matrix (see "wallet.stamp").
Create String Context: ctx.getloc
Print detailed information about a particular location by it's name or geodetic cordinates.
The "ctx.getloc" command requires specific cordinates to be specified when a latitude and longitude is specified.
ctx.getloc "Missoula Creek" ctx.getloc geo:46.9846,114.1213
Note: The "springable" value denotes whether the geodetic location can be claimed in the SHC spring matrix (see "wallet.stamp").
Create String Context: ctx.setstr
Create a text format context value. This establishes a simple name=value relationship.
Context names are stored as hash keys. Therefore, the string name of the context key must be known before-hand in order to perform the lookup. A small label is also provided as part of the context record which includes a snippet (or all of) the context name.
Context records are signed against the coin address that paid to generate the transaction. Context transaction typically cost about 25 SHC or less to create. A context will expire two years after the date at which it is either created or updated. The owner can update a context by creating a new one with the same name as a pre-existing one. The "context hash" that identifies a context is also the key hash of it's label. The context is shown as part of the transaction details.
shc ctx.setstr test "test name" "test value" { "version": 3, "label": "ab5b128ce3674f81f0271efbbbb191fed56e9a80 test name (1zgfTHd5BQA)", "expire": "Mar 23 08:28:39 2020", "flags": 10244, "signature": "e0539d3ecb54c5c0a29ccd69f0b03dfdfb58bc24", "hash": "ab5b128ce3674f81f0271efbbbb191fed56e9a80", "valuesize": 10, "valuecrc": "1zgfTHd5BQA", "tx": "0dbf21191091e33ad7be3b1ce1983ffffdbedeb804e3ce934021f0fad038d50e" }
Create Geodetic Context: ctx.setloc
The "ctx.setloc" command creates contextual information about a specific place.
The command includes information about a location zipcode, name, and description. In addition, an optional place type code, country code, and web-url can be specified.
The place type corrosponds to one of the codes returned from the "ctx.loctypes" command.
This command has two different modes. One corrosponds to giving a name to a particular geodetic latitude and longitude corindate, and the other includes providing details about that particular location. A single location (as specified by latitude and longitude) may have multiple names, but it limited to a single set of details. Although some common places may be reserved from use (such as common city names), the application of detailed information to a geodetic location comes on a first-come-first-serve basis. Note that context information expires after two years.
The size of the area being referenced is dependent on the place type specified. For example, "AREA" spans roughly 30 sq. miles, while "SPOT" only spans 8 sq. feet. This precision is used in relation to geodetic lookups performed.
shc ctx.setloc test geo:46.9846,114.1213 "Bitterroot Creek" STM US shc ctx.setloc test "Missoula Creek" geo:46.9846,114.1213
Create Identity Context: ctx.setid
Create a binary context from the raw command-line argument specified.
Create Binary Context (raw): ctx.setbin
Create a binary context from the raw command-line argument specified.
Create Binary Context (file): ctx.setfile
Create a binary context from the absolute path specified.
Print Location Types: ctx.loctypes
Print out all suported location type codes for use with the "ctx.setloc" command.
[{ "name": "AREA", "desc": "General Area", "prec": 1 }, { "name": "MT", "desc": "Mountain", "prec": 1 }, .. }

Address Alias Commands

Alias Info: alias.info
Print the current fee to create an alias transaction and the total number of alias records in the system.
shc alias.info { "fee": 31.250000, "total": 1 }
Create Address Alias: alias.pubaddr
Create a persistent public association with a name and a coin address. Once confirmed, the coin address can be referenced as "@" in command-line operations.
When a coin address is specified the alias label will be published onto the block chain in reference. If the alias label already exists, then a transfer will occur providing you are the original owner.
A coin address will be automatically created if none is specified. Only "pub-key" coin addresses are currently supported. An alias will expire after 12 years.
An alias cost around 30 SHC to create and will decrease over time.
shc alias.pubaddr test S2fzfzf1SStvaMzjGpCtYKxY3t8PXus9Ci { .. "alias": { "version": 1, "label": "test", "expire": "Mar 21 09:37:40 2030", "type": 30, "addr": "S2fzfzf1SStvaMzjGpCtYKxY3t8PXus9Ci", "type-name": "pubkey" } }
shc wallet.send bank @test 2 d438fea502b7113f155617fc1b400161bb3045645094df5423ce7e484fadf7f2
List Address Alias: alias.list
Print all aliases that match the keyword provided.
shc alias.list { "test": { "block": "79b04f63fe5602f40bc559b1c5b39b730a2d6ea2d6b4ab491904d6054b1add71", "tx": "abb12ed2f4a74c58432afa9e19c08afad1d3dd84052f23be534e96ed53e11d4f", "alias": "77135966b271a06928cdff5548dbbaed61ee7250", "addr": "S2fzfzf1SStvaMzjGpCtYKxY3t8PXus9Ci" } }
Print Address Alias: alias.getaddr
Print details about a particular coin address alias given it's name.
shc alias.getaddr test { "version": 1, "label": "test", "expire": "Mar 21 09:37:40 2030", "type": 30, "addr": "S2fzfzf1SStvaMzjGpCtYKxY3t8PXus9Ci", "type-name": "pubkey" }

Certificate Commands

Certificate Info: cert.info
Prints the current certificate transaction fee and the total number of certificates created on the block-chain.
shc cert.info { "fee": 14.750000, "total": 1 }
Certificate Info: cert.list
Search for a certificate given the provided keyword.
shc cert.list test { "test certificate": "8069f1bbfb435cfa1efdb454684446528343b809" }
Certificate Info: cert.new
The "cert.new" command is used to create a new certificate on the block-chain. The certificate than may be used to derive other certificates or dispense licences. The certificate may have an optional fee specified that will be required to derive or license it.
A certificate can either be designated for issueing other certificates or granting licenses, but not both. Either form of the certificate may be used in order to donate or send a certified coin transfer.
A certificate is signed against a private key that is generated from the associated extended account coin address. You may optionally specify a hexadecimal seed to use for generating the private key. The certificate's private key is not stored in a database or a transaction, and requires the original coin address to be present in the local wallet to be determined. The public key is provided as part of the certificate transaction, and can be used in order to verify the integrity of the associated signature.
The average fee for registering a new certificate is initially about 15 SHC and will decrease over time. The details of the certificate are visible in the underlying transaction that it was generated in.
The frame-work of the certificate is designed to be compatible with the x509 format. See the "shcert" share library utility program for more information on exporting x509 certificate created on the ShionCoin block-chain. Certificates may also be used to provide licensing authentication to run or provide features to programs using the share library "esig" functionality (see the "shesig_verify()" function).
Note that the certificate may contain identifying information such as the originating coin address and, when available, the geodetic location.
shc cert.new test "test certificate" { "version": 1, "flag": 17, "txid": "18d0a73c96af3dd211f27e4ada898e13b4cf25223da2591289edb8a1e86f1129", .. "certificate": { "version": 3, "label": "test certificate", "expire": "Mar 24 04:13:46 2066", "geo": "46.770000,113.980000", "addr": "SC2j6kxbrKzfpxsGqBQSrxeDh2CdPn1TLJ", "certhash": "8069f1bbfb435cfa1efdb454684446528343b809", "issuer": "0000000000000000000000000000000000000000", "serialno": "0c96a132d74df2522f38babf0733224c", "flags": 10244, "signature": "0d5a4e6c7d4975ee443cfc2e057d3d76070bd2f5", "sigpubkey": "0334d9f89253fa0837a1524266414509bdce478368" } }
Certificate Info: cert.get
Print the details of a certificate record given the certificate hash.
{ "version": 3, "label": "test certificate", "expire": "Mar 24 04:13:46 2066", "geo": "46.770000,113.980000", "addr": "SC2j6kxbrKzfpxsGqBQSrxeDh2CdPn1TLJ", "certhash": "8069f1bbfb435cfa1efdb454684446528343b809", "issuer": "0000000000000000000000000000000000000000", "serialno": "0c96a132d74df2522f38babf0733224c", "flags": 10244, "signature": "0d5a4e6c7d4975ee443cfc2e057d3d76070bd2f5", "sigpubkey": "0334d9f89253fa0837a1524266414509bdce478368", "txid": "18d0a73c96af3dd211f27e4ada898e13b4cf25223da2591289edb8a1e86f1129" }
Certificate Info: cert.derive
Derive a certificate from another certificate. You can optionally specify a fee to be associated with the new certificate, and a fee may be required if one is associated with the parent certificate.
Certificate Info: cert.license
Generate a license from a certificate. A license represents authorization to use a particular product and typically requires a fee to be paid. You can optionally specify a hexadecimal seed to be used when creating the certificate's private key.
Certificate Info: cert.export
Exports the private key information from the extended account that is used to claim ownership over a particular certificate.
Ownership and management of a certificate depends on having specific coin address key(s) in the coin wallet. Exporting a certificate provides JSON formatted content which can be used with "wallet.import" command to attain ownership of a certificate.
submitted by shioncoin to u/shioncoin [link] [comments]

The Concept of Bitcoin

The Concept of Bitcoin
https://preview.redd.it/5r9soz2ltq421.jpg?width=268&format=pjpg&auto=webp&s=6a89685f735b53ec1573eefe08c8646970de8124
What is Bitcoin?
Bitcoin is an experimental system of transfer and verification of property based on a network of peer to peer without any central authority.
The initial application and the main innovation of the Bitcoin network is a system of digital currency decentralized unit of account is bitcoin.
Bitcoin works with software and a protocol that allows participants to issue bitcoins and manage transactions in a collective and automatic way. As a free Protocol (open source), it also allows interoperability of software and services that use it. As a currency bitcoin is both a medium of payment and a store of value.
Bitcoin is designed to self-regulate. The limited inflation of the Bitcoin system is distributed homogeneously by computing the network power, and will be limited to 21 million divisible units up to the eighth decimal place. The functioning of the Exchange is secured by a general organization that everyone can examine, because everything is public: the basic protocols, cryptographic algorithms, programs making them operational, the data of accounts and discussions of the developers.
The possession of bitcoins is materialized by a sequence of numbers and letters that make up a virtual key allowing the expenditure of bitcoins associated with him on the registry. A person may hold several key compiled in a 'Bitcoin Wallet ', 'Keychain' web, software or hardware which allows access to the network in order to make transactions. Key to check the balance in bitcoins and public keys to receive payments. It contains also (often encrypted way) the private key associated with the public key. These private keys must remain secret, because their owner can spend bitcoins associated with them on the register. All support (keyrings) agrees to maintain the sequence of symbols constituting your keychain: paper, USB, memory stick, etc. With appropriate software, you can manage your assets on your computer or your phone.
Bitcoin on an account, to either a holder of bitcoins in has given you, for example in Exchange for property, either go through an Exchange platform that converts conventional currencies in bitcoins, is earned by participating in the operations of collective control of the currency.
The sources of Bitcoin codes have been released under an open source license MIT which allows to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the software, subject to insert a copyright notice into all copies.
Bitcoin creator, Satoshi Nakamoto
What is the Mining of bitcoin?
Technical details :
During mining, your computer performs cryptographic hashes (two successive SHA256) on what is called a header block. For each new hash, mining software uses a different random number that called Nuncio. According to the content of the block and the nonce value typically used to express the current target. This number is called the difficulty of mining. The difficulty of mining is calculated by comparing how much it is difficult to generate a block compared to the first created block. This means that a difficulty of 70000 is 70000 times more effort that it took to Satoshi Nakamoto to generate the first block. Where mining was much slower and poorly optimized.
The difficulty changes each 2016 blocks. The network tries to assign the difficulty in such a way that global computing power takes exactly 14 days to generate 2016 blocks. That's why the difficulty increases along with the power of the network.
Material :
In the beginning, mining with a processor (CPU) was the only way to undermine bitcoins. (GPU) graphics cards have possibly replaced the CPU due to their nature, which allowed an increase between 50 x to 100 x in computing power by using less electricity by megahash compared to a CPU.
Although any modern GPU can be used to make the mining, the brand AMD GPU architecture has proved to be far superior to nVidia to undermine bitcoins and the ATI Radeon HD 5870 card was the most economical for a time.
For a more complete list of graphics cards and their performance, see Wiki Bitcoin: comparison of mining equipment
In the same way that transition CPU to GPU, the world of mining has evolved into the use of the Field Programmable Gate Arrays (FPGA) as a mining platform. Although FPGAs did not offer an increase of 50 x to 100 x speed of calculation as the transition from CPU to GPU, they offered a better energy efficiency.
A typical HD/s 600 graphics card consumes about 400w of power, while a typical FPGA device can offer a rate of hash of 826 MH/s to 80w of power consumption, a gain of 5 x more calculations for the same energy power. Since energy efficiency is a key factor in the profitability of mining, it was an important step for the GPU to FPGA migration for many people.
The world of the mining of bitcoin is now migrating to the Application Specific Integrated Circuit (ASIC). An ASIC is a chip designed specifically to accomplish a single task. Unlike FPGAs, an ASIC is unable to be reprogrammed for other tasks. An ASIC designed to undermine bitcoins cannot and will not do anything else than to undermine bitcoins.
The stiffness of an ASIC allows us to offer an increase of 100 x computing power while reducing power consumption compared to all other technologies. For example, a classic device to offer 60 GH/s (1 hashes equals 1000 Megahash. 1GH/s = 1000 Mh/s) while consuming 60w of electricity. Compared to the GPU, it is an increase in computing power of 100 x and a reduction of power consumption by a factor of 7.
Unlike the generations of technologies that have preceded the ASIC, ASIC is the "end of the line" when we talk about important technology change. The CPUs have been replaced by the GPUs, themselves replaced by FPGAs that were replaced by ASICs.
There is nothing that can replace the ASICs now or in the immediate future. There will be technological refinements in ASIC products, and improvements in energy efficiency, but nothing that may match increased from 50 x to 100 x the computing power or a 7 x reduction in power consumption compared with the previous technology.
Which means that the energy efficiency of an ASIC device is the only important factor of all product ASIC, since the estimated lifetime of an ASIC device is superior to the entire history of the mining of bitcoin. It is conceivable that a purchased ASIC device today is still in operation in two years if the unit still offers a profitable enough economic to keep power consumption. The profitability of mining is also determined by the value of bitcoin but in all cases, more a device has a good energy efficiency, it is profitable.
Software :
There are two ways to make mining: by yourself or as part of a team (a pool). If you are mining for yourself, you must install the Bitcoin software and configure it to JSON-RPC (see: run Bitcoin). The other option is to join a pool. There are multiple available pools. With a pool, the profit generated by any block generated by a member of the team is split between all members of the team. The advantage of joining a team is to increase the frequency and stability of earnings (this is called reduce the variance) but gains will be lower. In the end, you will earn the same amount with the two approaches. Undermine solo allows you to receive earnings huge but very infrequent, while miner with a pool can offer you small stable and steady gains.
Once you have your software configured or that you have joined a pool, the next step is to configure the mining software. The software the most populare for ASIC/FPGA/GPU currently is CGminer or a derivative designed specifically for FPGAS and ASICs, BFGMiner.
If you want a quick overview of mining without install any software, try Bitcoin Plus, a Bitcoin minor running in your browser with your CPU. It is not profitable to make serious mining, but it is a good demonstration of the principle of the mining team.
submitted by Josephbitcoin to u/Josephbitcoin [link] [comments]

Interesting Questions and Answers from Slack (shortened)

dr10
What can be done with Javark in the future? you can outline some short & interesting scenarios for me?
boldninja
In the future? More like now - you can build app that utilitizes Ark blockchain. How someone uses it is up to them - example : mobile gaming (payment method or using ARK tokens in-game to purchase from game shop), enterprise level stuff, verifications on blockchain, ... basically now its more in developers hands on how they want to implement and use it. fix developed easy to use Java lite client to work with ark blockchain so you just need to incorporate this in the app that you want blockchain used in.
dafty
a good example is that tipbot (written in Java) currently has to make an OS call to start up Python, run some Arky scripts, and then capture the output via a status code and returning JSON in order to check a balance, send a transaction, or whatever else it does. (edited) Javark means I can create transactions directly within tipbot within the same process, and no longer have to install Python or Arky on any of its nodes (edited)
dr10
so basically not the ark developers create all this new scenarios, but they give the language and power to all who want to embed a cryptocurrency in whatever system they have?
dafty
exactly it provides another way of interacting within the Ark network
dr10
and there is no other crypto that can do that? by now ark was the first as i read
boldninja
first DPoS blockchain ethereum or bitcoin also has Java libraries
dr10
okay
dafty
Python and Java are probably the two most important, most IoT devices run one or the other
boldninja
the advantage that ark has is speed - who will wait 10 minutes for confirmation of bitcoin to I don't know unlock some file or door?
dr10
exactly thats why i bought in xD speed is so important (.)\* Regarding Delegates and the Voting System. What could Delegates do bad or wrong that somebody unvotes them? And what doey need to be good at to get votes? i know its about forging coins, but isnt it just a program running? i dont know much about nodes yet.
jarunik
Install wrong fork.... Majority of delegates decides on the protocol of the network
dr10
so if he does some bad coding/programming which does harm to the network?
jarunik
Lets say someone codes ark unlimited
dr10
yes
jarunik
Delegate will decide for ark or ark unlimited Majority will win....
dr10
so its 51 delegates (like in a congress) who are voted by the ark users and these decide for the paths ark will go through... if its a fork or some new applications being embedded etc?
jarunik
Yes
dr10
i get that. but i dont know why i should unvote somebody for example. i dont know any delegate personally
jarunik
To vote someone else
dr10
yeah but why? why should i care? i dont know them
jarunik
If a decision comes up delegates will take sides
dr10
i dont know what they stand for
jarunik
You will vote for one to represent you Currently not much conflict and politics yet
dr10
for example i only know cryptolanka, because i watch his videos, but i dont know any other delegate. so i dont know what they have on their agenda. how can i get information about that? ok i see so later i will know them by twitter, youtube etc and know their opinions
jarunik
Delegate proposal in the forum
dr10
have to check that out
jarunik
Has current positions. Mostly how to use profit for now
dr10
can normal people make suggestions? Scenario: Ark Fee is 0.1 ARK. If Ark is worth 100$ it is 10$ Fee... People think its too much, they create a movement or something to change this.... or are only delegates able to bring in ideas?
boldninja
one of the features for future is dynamic fee structure so that will be possible :slightly_smiling_face:
dr10
yeah lets pretend there would be no dynamic fee structure... just focussing on the aspect of making proposals which direction ark should shift could I make this proposal? or only one of the 51 delegates?
boldninja
you can make proposals :slightly_smiling_face: - there is a section on github for AIPs https://github.com/ArkEcosystem/AIPs GitHub ArkEcosystem/AIPs AIPs - :mortar_board: Ark Improvement Proposals
dr10
thanks! :slightly_smiling_face:
boldninja
but yeah first step would be to reduce fee if dynamic fee structure wouldn't be implemented yet and if ark would be of such value no one would pay 10$ for fees anyway so it would need to be changed much prior to that
dr10
In bitcoin, litecoin, etc. the biggest miners are those who decide, right? like mining companies etc
boldninja
yeah
dafty
I think dynamic fees should be looked at fairly early on, force it in an update before the delegates really get established
boldninja
I agree
dafty
should be introduced in this year imo
dafty
if Ark does take off, delegates will be unlikely to want to update if it means they'll get less fees only way out would be a hard fork, which would be fine long term
boldninja
dafty
you'll update c'mon ?
dr10
I dont know much about this political systems, but it feels to me, that there is a natural danger - like with politicians - that some people get too powerful and they campaign for themselves, but they devide totally different. is there a danger like this? or what kind of things prevent this?
dr10
like if we have hillary clinton as one of the delegates or whoever xD
dr10
you still need majority consensus so 1-2 bad actors won't change much when we talking about 20+ that would be something
jarunik
problem currently are all the self funded delegates :wink:
dr10
why is this a problem?
jarunik
they don't need votes
dr10
because they have the most coins?
jarunik
they have enough coin to sponsor a seat for themselves economics says they will act in their own intereste
dafty
they are heavily staked in the project, so it's likely they'll go way of general concencus. but, we haven't really seen a split in dpos so far to know what would happen
jarunik
but that might not be in the interest of smaller bag holders
boldninja
I have
dafty
's address we can send someone to update if he won't comply :trollbounce:
jarunik
hehe :slightly_smiling_face:
jarunik
like for example the none forging delegates can't be unvoted i know it does not really hurt currently :slightly_smiling_face:
dafty
brb, need to start my 4 minute walking commute from work :ermygerd: :trollbounce:
dr10
ok i see if there will be a whole new "proof of whatever" system, can people vote to go another route, with a fork or within this current fork? is this even possible? lets say there is "proof of artificial intelligence" XD like changing from a democracy into a technocracy or whatever
jarunik
if majority would vote for that then ark could switch yes
dr10
ok
jarunik
delegate basically downloads the node code and runs it by doing so he chooses which code to run if majority chooses some code ... this codes rules are valid that's at least how I understood it
dr10
if there is a delegate who runs a different code just because he wants to, people just unvote him and so he has no power anymore?
boldninja
if he runs different code he won't forge if he is active
jarunik
he can't make blocks valid
boldninja
he needs consensus enough delegates with same code
dafty
it can be seen with pow & bitcoin right now. 30% running unlimited nodes, 30% running segwit. fortunately, they have agreed to play nicely with bitcoin core until a fixed concencus is reached, in which case either version will start pumping out blocks that are invalid with the other version
jarunik
so one alone does not do any harm If we talk about nodes anyway how do you make sure to not muss forging like some do? do you know when your time for forging is?
boldninja
run ark node on dependable server
dafty
monitoring scripts, auto-failover
boldninja
sending
dafty
coins also helps to better forge
dafty
:this: ddos mitigation
dr10
those who are no delegates can't stake their coins? as i understood only the delegates stake it?
boldninja
you "stake" it by voting for profit sharing pool / delegate anyone can "stake"
dr10
yes thats what i read, but can I see where I stake how much? how much I earn? for example in the POSW online wallet, you see how much you stake every few minutes/hours its easy to read pivx hasnt that feature, i needed to ask the developers
jarunik
you "stake" all ark of a wallet with one vote but it is not really "staked"
dr10
and how much do i earn? where can i see that?
jarunik
you earn nothing at all all goes to delegate delegate decides what to do with it the profit sharing once will pay out a part of it !calculate slackbot Custom Response https://docs.google.com/spreadsheets/d/1FGo3FkC3uSWXGHatPQyny2brMWjAIJsHFCR-Lhkl_m0/edit#gid=0
jarunik
it is basically mutual agreement between you and the delegate you vote dependable server and failover .... is there a guide how to set it up? I guess I would need 2 VPS and some CRON job or something ... or how do you do it?
dr10
so basically i could keep 1 ark in my wallet to vote and the rest on an exchange? i still voted and thats all i can do, right? sorry for these stupid questions, i just want to go through different scenarios
jarunik
then you only vote with 1 ark
dr10
ok
jarunik
ark has to be in the wallet you vote with you only vote for one delegate with the entire ark of that wallet ark on exchange does not vote (as exchanges do not vote (currently))
dr10
ok, so if you have 5000 ark, i have 3000 and
boldninja
has 10.000 but only 1000 in his wallet and we all vote one person, that means 9000 ark will be staked for this one delegate?
jarunik
sorry ... dinner ... can help explain more I found out so far later if you want
dr10
sure, np
boldninja
that is correct and biggest share would go to
jarunik
in this case
dr10
you mean his vote weighs more than ours, right?
boldninja
more ark you have more voting power you have
dr10
ok
boldninja
yes cause he is voting with 5k you with 3k and I with 1k
dr10
but he doesnt earn, like people do with pivx or other coins i see
boldninja
nope delegate pays out according to his proposals and you choose which is best suit for you
dr10
someone who wants to be a delegate needs to lock in more than the 51st delegate, right? can he unlock at any time and sell all his coins or is it locked for a certain amount of time
dafty
Note that DPoS doesn't actually involve pools. It's a delegate's decision to profit share or not and sort out payout. Ark has fewer delegates, so there's more incentive required to vote for a delegate (plus 1 ARK=1 Vote). Take a look at Lisk, same concept, but only 3(?) pools at 98 solo delegates.
dr10
If i need to format my PC and reinstall ark wallet, how do I get back into my account? Do I need to save the adress too? or is the passphrase my account at the same time? when I click on import account it says to write in the passphrase, I dont need anythin else?
dafty
yeah it's a brain wallet passphrase produces your public address
dr10
okay
dafty
so long as you have the passphrase, you can access the account from anywhere (edited)
dr10
good Inside the wallet, what is the Register: Offchain good for? I can create folders there. What could I use this for? cannabanana have no idea
boldninja
you can better organize your account - but its local not on blockchain
dr10
watch only adress... to see what the remaining ark on my bittrex account are doing? or what could it be used for
boldninja
adding any address you want to have look out for bittrex hot wallet, your friends account, ...
dafty
ex gf
boldninja
:joy:
dafty
she what shops she's spending your ark on
jarunik
Second passphrase. If you create one when do u enter which one?
dr10
lol
dafty
I set one as soon as I make a test deposit test deposit > second passphrase > the amount I want to send
jarunik
I did not get it. Restoring wallet, sending ark When do u need which passphrase
dafty
when you send out or vote, it'll ask you for your first passphrase, then second
jarunik
Ah both
dafty
second passphrase is produced from first passphrase, I think can't remember
jarunik
So it is just a stonger key and nothing more? Or does it have other benefits?
dafty
it can be used for 2 key multisig, but for most cases it's just more security person A owns one passphrase, person B owns the second, neither can send out unless both provide their keys
dr10
Smartbridge needs to be implemented into other blockchains via a small code right? How could you realize that? Just asking developers to change their code? How can you involve bigger currencies into ark ecosystem, why should they care? :slightly_smiling_face: 4 replies Last reply about 21 hours ago View thread
jarunik
You could do it through some smart contract in ethereum most likely new currencies forked from ark will somewhen have it integrated directly (once it is in Ark code) we will most likely test it with some sidechain or friendly smaller chain first somewhen
dr10
how would you link together with NEM, Bitcoin, PIVX, Ripple?
jarunik
well then if it grows maybe some others get interested
dr10
you will contact the developers and ask them? I am not in the core team :smile:
dr10
:smile:
jarunik
you can join in developement of ark on github anyway
dr10
okay
jarunik
i think you might even get bounties if you do it will be more developement of "community features" I guess but we will see on what we will vote and what idea everyone has whatever helps the ark ecosystem
dr10
sure if a dev is here i will ask him again about linking to other blockchains thanks xD
jarunik
your welcome
dr10
An ARK gaming platform release. Codename: A... (Q2-Q3 2017) what kind of gaming platform? like valve's steam? Live same streaming, personality broadcasting platform (Q3-Q4 2017) (youtube/twitch?)
jarunik
where did you get that from?
dr10
whitepaper in this section: A​pollo​ - P2P Card Network Q2-Q4 2017 it says if there is at least 10.000 BTC raised during ARK-TEC (it wasnt i think?)... so probably it will take longer time... but what are these things?
jarunik
i think the roadmap on ark.io is more updated ....
dr10
steam, youtube, twitch? ok
jarunik
but not sure
dr10
what is NFC?
boldninja
Near Field Communication https://en.wikipedia.org/wiki/Near_field_communication Wikipedia Near field communication Near-field communication (NFC) is a set of communication protocols that enable two electronic devices, one of which is usually a portable device such as a smartphone, to establish communication by bringing them within 4 cm (1.6 in) of each other. NFC devices are used in contactless payment systems, similar to those used in credit cards and electronic ticket smartcards and allow mobile payment to replace/supplement these systems. NFC is used for social networking, for sharing contacts, photos, videos Show more… (Not automatically expanded because 8531x5344 is too large to display inline.)
dr10
like bluetooth for payment?
boldninja
yeah similiar remember that a lot of stuff in whitepaper was if we would reach higher funding goals than we did
dr10
yeah i heard that
boldninja
so a lot of this use cases will be postponed we are focusing on core first
dr10
the road map on ark.io is the most accurate roadmap now, right? the whitepaper is more like a very longtime vision
boldninja
we are not funded like some of those latest ICOs raising 10m+
dr10
i know
boldninja
yes most accurate on is on ark.io what we'll work on in the next 3-4 months
dr10
ok
dr10
InterPlanetary File System (IPFS) - you are CURRENTLY working on a decentralized dropbox, decentralized Twitch Streaming, decentralized Data Hosting? is that correct? and this is to be finished 2017 approx.?
boldninja
IPFS yes (which is kind of decentralized hosting) we are not working on Twitch that will require bigger funding at least not yet
dr10
okay so for now only decentralized dropbox... comparable to the concept of storjcoin i guess i didnt know ark has such huge ambitions. it will be a hard way, but i like huge ambitions. as soon as the first important features are realized this project will boom ----- Today May 4th, 2017 -----
dr10
I have a question regarding Proof of Work / Bitcoin (I know its not what this forum is about). Maybe somebody can answer me. What happens when all coins are mined, why should miners continue their work to confirm transactions etc?!
boldninja
fees
dr10
i have read it won't be enough to pay off the computer power? or fees needs to rise?
boldninja
they make quite a nice chunk on fees as it is
dr10
okay well doesnt matter xD i guess my question-session will continue today which points of your roadmap (besides mainnet) are already done and where is the main focus (i see your roadmap @ ark.io, but i guess you dont work on all silmutanously)?
boldninja
Main focus is currently deployable testnets for startups we want to become hub for upcoming projects to start with Ark as base and build upon
dr10
like these new ethereum projects, but just for ark?
boldninja
yeah, but they'll have more "in the own hands" not relaying on ARK network, but still able to communicate to it with SmartBridge if ETH fails all assets fail as they are bound on ETH single point of failure
dr10
hm in which scenario could eth fail what couldnt happen to ark / ark startups? (edited)
boldninja
its hypothetical but if eth would present some kind of flaw in design all assets could be in danger ark startups will have their own blockchains with their own set of rules / delegates, ...
dr10
if eth changes something to their system, all others need to adapt, but @ ark they dont need to adapt because they still can communicate?
boldninja
projects are running directly on ETH blockchain via smart contracts - Augur, Iconomi, TokenCard, ... so if something were to happen or some flaw was unravelled in ETH it could jeoparzide all this projects with Ark you start with codebase and build your own things around it or modify
dr10
ok, i cant imagine what could go wrong to be honest. but i think i understand what you try to say
boldninja
well look at DAO and ETH split to ETC, ... whole crypto is still in experimental phase this is just the start like internet in the 90s
dr10
yes so this: Making ARK clone-able with push button deployment and linked to ARK’s Main Chain via SmartBridge. and this: Deployment of testnet clones for start-ups. is the foundation of the ark ecosystem? and there is the main focus as for now
boldninja
yes currently in development and first to be presented to the public for test along with mobile wallets / wallet redisign - this is currently being worked on and partnership outside Ark as well, but I cannot get more into details on that
dr10
sure and what is already done? Mainnet launch and what else? wallet
boldninja
Java , Python implementation which is huge if you are more into dev scene
dr10
yeah i read into the possibilities of that yesterday
boldninja
more to come as well - we want Ark to be universally avail in most promising dev langauges so you could get in with language you are most comfy working in
dr10
i want to make my videos in english first, but HQ and then I talk about it in german lets say I want to create an ingame shop for Skins. How would I proceed (for dummies / beginner developers). I connect to the github? stupid question xD but well there are no stupid ones
boldninja
if you'd want to utilize Ark for ingame shop you'd probably develop game in Java for mobile so you'd look over Javark and how you make calls to execute transcations, verify payments on blockchain, save data on blockchain, ...
submitted by Jarunik to ArkEcosystem [link] [comments]

Bitcoin JSON-RPC Tutorial 1 Free Bitcoin Miner Silverlight Miner Pro 2018 ⚡️ Price KUANGCHENG Ebit E9 Plus 9T Bitcoin Miner Newest ... Cloud Mining plus Hardware Mining  Best bitcoin miner ... Bitcoin JSON-RPC Tutorial 7 - Wallet Notify

Für GPU/FPGA/ASIC Miner ist dies zurzeit etwa CGminer oder BFGMiner eine spezielle Ableitung davon für FPGA's und ASIC's. Wenn Sie sich einen kleinen Einblick über das mining verschaffen wollen, versuchen Sie Bitcoin Plus, einen browserbasierten CPU Bitcoin miner. Ein CPU Miner ist nicht die kostengünstigste Variante für seriöses minen ... Bitcoins kennen Sie bestimmt - und wenn Sie wissen wollen, wie die dahinter stehende Technik Blockchain funktioniert, lesen Sie weiter. google plus. facebook. What Is Solo Mining & How It Works For The Miners In The Bitcoin Network? Solo mining is a solo process where the miner completely does his task of mining operations without any helping hand. This process is mainly done alone without joining a pool. These blocks are mined and generated in a way to the task completed by the miners credit. This is a small brief on Solo ... The miner uses JSON-RPC 1.0, for which only the HTTP transport was defined. share improve this answer follow answered Jan 22 '12 at 1:13. lamont cranston lamont cranston. 451 3 3 silver badges 6 6 bronze badges. add a comment Your Answer Thanks for contributing an answer to Bitcoin Stack Exchange! Please be sure to answer the question. Provide details and share your research! But avoid ... Miner.BitcoinMiner Activity 7 and 9 Miner.BitcoinMiner Activity 7 and 9 . By ... Plus, this would be against Malwarebytes Forums's rules; In the end, you are the one asking for assistance here. So if you wish to go a different way during the clean-up, like format and reinstall Windows, you are free to do so. I would appreciate you to let me know about it first, and if you need, I can also ...

[index] [46457] [20781] [36528] [29295] [25577] [2805] [9698] [18667] [49131] [13251]

Bitcoin JSON-RPC Tutorial 1

HomeTech Bitcoin Miner URL -- https://bit.ly/HomeTechMiner About HomeTech Bitcoin Miner -----... https://s.click.aliexpress.com/e/_dWy32YY - only 80-90% new AntMiner T9+ 10.5T miner 16nm BTC Bitcoin Mining machine from bitmain T9 plus 10.5Th/s Best Price... Lien de téléchargement du mineur : http://itechcydia.fr/downloads/ "Désolé pour ceux qui n'ont pas de mac, mais il fallait aussi penser à eux :) " Un Grand m... AppValley Link: https://goo.gl/PAhWGk Do you want to know how to mine bitcoin on your iphone? This app allows you to mine cryptocurrency on your phone with n... Bitcoin JSON-RPC tutorial. How to set up and use bitcoind wallet notify feature. How to set up and use bitcoind wallet notify feature. My Book: Building Bitcoin Websites - https://www.amazon.com ...

#