| select d.github_source, e.* from | |
| (select a.github_source, count(*) as count FROM | |
| (SELECT DISTINCT github_source FROM assignments) as sources | |
| INNER JOIN assignments as a ON sources.github_source = a.github_source group by a.github_source) as d | |
| inner join assignments as e on d.github_source = e.github_source where d.count > 1; | |
| results = ActiveRecord::Base.connection.execute( | |
| 'select d.github_source, e.* from | |
| (select a.github_source, count(*) as count FROM | |
| (SELECT DISTINCT github_source FROM assignments) as sources |
| results = ActiveRecord::Base.connection.execute( | |
| 'select d.github_source, e.* from | |
| (select a.github_source, count(*) as count FROM | |
| (SELECT DISTINCT github_source FROM assignments) as sources | |
| INNER JOIN assignments as a ON sources.github_source = a.github_source group by a.github_source) as d | |
| inner join assignments as e on d.github_source = e.github_source where d.count > 1;' | |
| ) | |
| with_content_ids = [] | |
| no_content_ids = [] |
| curl http://elasticsearch05.fe.flatironschool.com:9200/users_development/_search?pretty -d '{ | |
| "query":{ | |
| "dis_max":{ | |
| "queries":[ | |
| { | |
| "match":{ | |
| "github_username.analyzed":{ | |
| "query":"adam", | |
| "operator":"and", | |
| "boost":10, |
| #!/usr/local/rvm/rubies/ruby-2.3.3/bin/ruby | |
| require 'net/http' | |
| require 'json' | |
| MONITORED_HOSTGROUPS = { | |
| ironboard: 'Web Servers', | |
| postgres: 'Database', | |
| flatchat: 'Chat', | |
| ide: 'IDE' |
| 1) How can Gossip protocol be exploited to leak privacy? | |
| 2) How do BOLT 11 strings potentially leak privacy? | |
| 3) What is the minimal amount of info watchtowers need to know to work? | |
| 4) How can we minimize what is broadcasted to the base layer and how can the base layer leak our privacy? |
| Fungibility/Privacy: | |
| Scalability: | |
| Trustlessness/Decentralization: |
src :
Let’s start by what you can do while typing. These keystrokes change only what happens on the input line (the line where you type stuff).
arrow left/right: move one character left or right.
Error:
>>> [do_build] Command failed: git apply /Users/jonas/bitcoin-dir/bitcoin-maintainer-tools/patches/stripbuildinfo.patch
>>> [do_build] Could not apply patch to strip build info. Probably it needs to be updated
Checkout the patchset from the last patch:
git checkout 'master@{aug 1}'
bitcoin/bitcoin#16401 - package relay
bitcoin/bitcoin#16702 - asmap to improve bucketing
bitcoin/bitcoin#16974 - Walk pindexBestHeader back to ChainActive().Tip() if it is invalid
bitcoin/bitcoin#16856 - Do not allow descendants of BLOCK_FAILED_VALID blocks to be BLOCK_FAILED_VALID
bitcoin/bitcoin#16939 - p2p: Delay querying DNS seeds if addrman is populated
Q: In this video, John Newbery talks about verification vs computation, and he bring it up as a big reason why he thinks bitcoin can scale but is skeptical about ethereum. I think I get the general idea of what he’s saying but I might be missing something.
Is there a qualitative difference between verification and computation? And is it the fact that ethereum is capable of performing arbitrary computation that makes the whole thing difficult to scale, or is it that specifically smart contracts that require arbitrary computation won’t be able to scale (as in those contracts would be very expensive to run).
A: There is a big difference between verification and computation.
For instance: