Download - Bitcoin
- Download - Bitcoin
- Bitcoin Money Adder V6.0 Activation Code Free ...
- unable to start & sync bitcoin qt · Issue #7724 · bitcoin ...
- Bitcoin Core :: Bitcoin Core 0.12.1
- Bitcoin Core version 0.12.1 released
Gridcoin 18.104.22.168-Mandatory "Fern" Release
https://github.com/gridcoin-community/Gridcoin-Research/releases/tag/22.214.171.124 submitted by jamescowens to gridcoin [link] [comments]
Finally! After over ten months of development and testing, "Fern" has arrived! This is a whopper. 240 pull requests merged. Essentially a complete rewrite that was started with the scraper (the "neural net" rewrite) in "Denise" has now been completed. Practically the ENTIRE Gridcoin specific codebase resting on top of the vanilla Bitcoin/Peercoin/Blackcoin vanilla PoS code has been rewritten. This removes the team requirement at last (see below), although there are many other important improvements besides that.
Fern was a monumental undertaking. We had to encode all of the old rules active for the v10 block protocol in new code and ensure that the new code was 100% compatible. This had to be done in such a way as to clear out all of the old spaghetti and ring-fence it with tightly controlled class implementations. We then wrote an entirely new, simplified ruleset for research rewards and reengineered contracts (which includes beacon management, polls, and voting) using properly classed code. The fundamentals of Gridcoin with this release are now on a very sound and maintainable footing, and the developers believe the codebase as updated here will serve as the fundamental basis for Gridcoin's future roadmap.
We have been testing this for MONTHS on testnet in various stages. The v10 (legacy) compatibility code has been running on testnet continuously as it was developed to ensure compatibility with existing nodes. During the last few months, we have done two private testnet forks and then the full public testnet testing for v11 code (the new protocol which is what Fern implements). The developers have also been running non-staking "sentinel" nodes on mainnet with this code to verify that the consensus rules are problem-free for the legacy compatibility code on the broader mainnet. We believe this amount of testing is going to result in a smooth rollout.
Given the amount of changes in Fern, I am presenting TWO changelogs below. One is high level, which summarizes the most significant changes in the protocol. The second changelog is the detailed one in the usual format, and gives you an inkling of the size of this release.
Note that the protocol changes will not become active until we cross the hard-fork transition height to v11, which has been set at 2053000. Given current average block spacing, this should happen around October 4, about one month from now.
Note that to get all of the beacons in the network on the new protocol, we are requiring ALL beacons to be validated. A two week (14 day) grace period is provided by the code, starting at the time of the transition height, for people currently holding a beacon to validate the beacon and prevent it from expiring. That means that EVERY CRUNCHER must advertise and validate their beacon AFTER
the v11 transition (around Oct 4th) and BEFORE
October 18th (or more precisely, 14 days from the actual date of the v11 transition). If you do not advertise and validate your beacon by this time, your beacon will expire and you will stop earning research rewards until you advertise and validate a new beacon. This process has been made much easier by a brand new beacon "wizard" that helps manage beacon advertisements and renewals. Once a beacon has been validated and is a v11 protocol beacon, the normal 180 day expiration rules apply. Note, however, that the 180 day expiration on research rewards has been removed with the Fern update. This means that while your beacon might expire after 180 days, your earned research rewards will be retained and can be claimed by advertising a beacon with the same CPID and going through the validation process again. In other words, you do not lose any earned research rewards if you do not stake a block within 180 days and keep your beacon up-to-date.
The transition height is also when the team requirement will be relaxed for the network.
Besides the beacon wizard, there are a number of improvements to the GUI, including new UI transaction types (and icons) for staking the superblock, sidestake sends, beacon advertisement, voting, poll creation, and transactions with a message. The main screen has been revamped with a better summary section, and better status icons. Several changes under the hood have improved GUI performance. And finally, the diagnostics have been revamped.
The wallet sync speed has been DRASTICALLY improved. A decent machine with a good network connection should be able to sync the entire mainnet blockchain in less than 4 hours. A fast machine with a really fast network connection and a good SSD can do it in about 2.5 hours. One of our goals was to reduce or eliminate the reliance on snapshots for mainnet, and I think we have accomplished that goal with the new sync speed. We have also streamlined the in-memory structures for the blockchain which shaves some memory use.
There are so many goodies here it is hard to summarize them all.
I would like to thank all of the contributors to this release, but especially thank @cyrossignol, whose incredible contributions formed the backbone of this release. I would also like to pay special thanks to @barton2526, @caraka, and @Quezacoatl1, who tirelessly helped during the testing and polishing phase on testnet with testing and repeated builds for all architectures.
The developers are proud to present this release to the community and we believe this represents the starting point for a true renaissance for Gridcoin!
Most significantly, nodes calculate research rewards directly from the magnitudes in EACH superblock between stakes instead of using a two- or three- point average based on a CPID's current magnitude and the magnitude for the CPID when it last staked. For those long-timers in the community, this has been referred to as "Superblock Windows," and was first done in proof-of-concept form by @denravonska.
- Network magnitude unit pinned to a static value of 0.25
- Max research reward allowed per block raised to 16384 GRC (from 12750 GRC)
- New CPIDs begin accruing research rewards from the first superblock that contains the CPID instead of from the time of the beacon advertisement
- 500 GRC research reward limit for a CPID's first stake
- 6-month expiration for unclaimed rewards
- 10-block spacing requirement between research reward claims
- Rolling 5-day payment-per-day limit
- Legacy tolerances for floating-point error and time drift
- The need to include a valid copy of a CPID's magnitude in a claim
- 10-block emission adjustment interval for the magnitude unit
- One-time beacon activation requires that participants temporarily change their usernames to a verification code at one whitelisted BOINC project
- Verification codes of pending beacons expire after 3 days
- Self-service beacon removal
- Burn fee for beacon advertisement increased from 0.00001 GRC to 0.5 GRC
- Rain addresses derived from beacon keys instead of a default wallet address
- Beacon expiration determined as of the current block instead of the previous block
- The ability for developers to remove beacons
- The ability to sign research reward claims with non-current but unexpired beacons
As a reminder:
- Beacons expire after 6 months pass (180 days)
- Beacons can be renewed after 5 months pass (150 days)
- Renewed beacons must be signed with the same key as the original beacon
- Magnitudes less than 1 include two fractional places
- Magnitudes greater than or equal to 1 but less than 10 include one fractional place
- A valid superblock must match a scraper convergence
- Superblock popularity election mechanics
- Yes/no/abstain and single-choice response types (no user-facing support yet)
- To create a poll, a maximum of 250 UTXOs for a single address must add up to 100000 GRC. These are selected from the largest downwards.
- Burn fee for creating polls scaled by the number of UTXOs claimed
- 50 GRC for a poll contract
- 0.001 GRC per claimed UTXO
- Burn fee for casting votes scaled by the number of UTXOs claimed
- 0.01 GRC for a vote contract
- 0.01 GRC to claim magnitude
- 0.01 GRC per claimed address
- 0.001 GRC per claimed UTXO
- Maximum length of a poll title: 80 characters
- Maximum length of a poll question: 100 characters
- Maximum length of a poll discussion website URL: 100 characters
- Maximum number of poll choices: 20
- Maximum length of a poll choice label: 100 characters
- Magnitude, CPID count, and participant count poll weight types
- The ability for developers to remove polls and votes
[126.96.36.199] 2020-09-03, mandatory, "Fern"
- Backport newer uint256 types from Bitcoin #1570 (@cyrossignol)
- Implement project level rain for rainbymagnitude #1580 (@jamescowens)
- Upgrade utilities (Update checker and snapshot downloadeapplication) #1576 (@iFoggz)
- Provide fees collected in the block by the miner #1601 (@iFoggz)
- Add support for generating legacy superblocks from scraper stats #1603 (@cyrossignol)
- Port of the Bitcoin Logger to Gridcoin #1600 (@jamescowens)
- Implement zapwallettxes #1605 (@jamescowens)
- Implements a global event filter to suppress help question mark #1609 (@jamescowens)
- Add next target difficulty to RPC output #1615 (@cyrossignol)
- Add caching for block hashes to CBlock #1624 (@cyrossignol)
- Make toolbars and tray icon red for testnet #1637 (@jamescowens)
- Add an rpc call convergencereport #1643 (@jamescowens)
- Implement newline filter on config file read in #1645 (@jamescowens)
- Implement beacon status icon/button #1646 (@jamescowens)
- Add gridcointestnet.png #1649 (@caraka)
- Add precision to support magnitudes less than 1 #1651 (@cyrossignol)
- Replace research accrual calculations with superblock snapshots #1657 (@cyrossignol)
- Publish example gridcoinresearch.conf as a md document to the doc directory #1662 (@jamescowens)
- Add options checkbox to disable transaction notifications #1666 (@jamescowens)
- Add support for self-service beacon deletion #1695 (@cyrossignol)
- Add support for type-specific contract fee amounts #1698 (@cyrossignol)
- Add verifiedbeaconreport and pendingbeaconreport #1696 (@jamescowens)
- Add preliminary testing option for block v11 height on testnet #1706 (@cyrossignol)
- Add verified beacons manifest part to superblock validator #1711 (@cyrossignol)
- Implement beacon, vote, and superblock display categories/icons in UI transaction model #1717 (@jamescowens)
- neuralnet: Add integrity checking to researcher accrual snapshot registry #1727 (@jamescowens)
- Add workaround for scrypt assembly on macOS #1740 (@cyrossignol)
- gui: Build onboarding/beacon wizard #1739 (@cyrossignol)
- doc: Add CONTRIBUTING.md from bitcoin #1723 (@div72)
- rpc: Implement inspectaccrualsnapshot and parseaccrualsnapshotfile #1744 (@jamescowens)
- scraper: Add disk based state backing for verified beacon list in scraper #1751 (@jamescowens)
- Add ability to recover beacon in block version 11+ #1768 (@cyrossignol)
- refactor: Add transaction context to contract handlers #1777 (@cyrossignol)
- gui: Add context for when BOINC is attached to a pool #1775 (@cyrossignol)
- doc: Clarify what to do if PR in multiple categories (for CONTRIBUTING.md) #1798 (@RoboticMind)
- qt: Add option to choose not to start the wallet minimized #1804 (@jamescowens)
- superblock: Add check for OutOfSyncByAge to SuperblockValidator::Validate #1806 (@jamescowens)
- contract: Standardize contract validation and add block context #1808 (@cyrossignol)
- add seed.gridcoin.pl to default config #1812 (@wilkart)
- gui: Implement sidestake send display #1813 (@jamescowens)
- gui: Add pool/investor pages to researcher wizard #1819 (@cyrossignol)
- ci: Port lint scripts from Bitcoin #1823 (@div72)
- doc: Create basic readme in contrib #1826 (@RoboticMind)
- gui: Implement TransactionRecord::Message #1829 (@jamescowens)
- rpc: Add private_key_available to beaconstatus #1833 (@a123b)
- gui: Validate email address in researcher wizard #1840 (@a123b)
- rpc: Add "getrawwallettransaction" RPC function #1842 (@cyrossignol)
- consensus: Set block version 11 threshold height for mainnet #1862 (@cyrossignol)
- Upgrade LevelDB from v1.17 to v1.20 #1562 (@cyrossignol)
- Re-enable scrypt optimizations #1450 (@denravonska)
- Derive CScript from prevector type (optimization) #1554 (@cyrossignol)
- Disable quorum for grandfathered blocks to speed up sync #1568 (@cyrossignol)
- Refactor hashBoinc for binary claim contexts #1558 (@cyrossignol)
- integrated_scraper_2 branch tracking PR #1559 (@jamescowens)
- Upgrade depends - OpenSSL to 1.1.1d #1581 (@jamescowens)
- Ubuntu 19.10 fixes #1590 (@denravonska)
- Force a re-parse of legacy claims in generated blocks #1592 (@cyrossignol)
- Improve the "versionreport" RPC output #1595 (@cyrossignol)
- Overhaul the core tally and accrual system #1583 (@cyrossignol)
- Overhaul the superblock quorum system #1597 (@cyrossignol)
- Add more data to the "superblocks" RPC output #1599 (@cyrossignol)
- Update Windows Build doc #1606 (@barton2526)
- Change the order of calls in gridcoinresearchd.cpp to optimize rpc shunt path #1610 (@jamescowens)
- Change staking tooltip to display frequency #1611 (@jamescowens)
- Enhancements to ETTS #1442 (@jamescowens)
- Standardize money values as integers #1614 (@cyrossignol)
- Clean up and optimize legacy coin age code #1616 (@cyrossignol)
- Some scraper cleanups #1620 (@jamescowens)
- Reorganize accrual code and fix 6-month cutoff #1630 (@cyrossignol)
- Update Copyright years #1633 (@barton2526)
- Change team whitelist delimiter to <> for CPID detection #1634 (@cyrossignol)
- Change team whitelist separator to <> to accomodate more team names #1632 (@jamescowens)
- Change Curl download speed type to support older environments #1640 (@cyrossignol)
- Optimize logo SVGs used for tray icons #1638 (@cyrossignol)
- Tweak consolidateunspent rpc function #1644 (@jamescowens)
- ETTS and staking icon enhancements #1650 (@jamescowens)
- Implement new transaction fees for block version 11 #1652 (@jamescowens)
- Optimize in-memory storage of superblock data #1653 (@cyrossignol)
- Miscellaneous superblock API improvements and housekeeping #1654 (@cyrossignol)
- Update openssl to 1.1.1f compatibility #1660 (@jamescowens)
- Optimize bdb to avoid synchronous flush of database #1659 (@jamescowens)
- Add support for CPID input to "lifetime" RPC function #1668 (@cyrossignol)
- Overhaul the contract handling system #1669 (@cyrossignol)
- Make the autostart mainnet/testnet aware #1671 (@jamescowens)
- Remove slashes from User Agent in peers tab #1674 (@div72)
- Refactor contracts for polymorphic binary payloads #1676 (@cyrossignol)
- Overhaul the beacon system #1678 (@cyrossignol)
- Replace boost::optional with non-owning pointers #1680 (@cyrossignol)
- Optimize proof-of-stake validation #1681 (@cyrossignol)
- Updated Slack link #1683 (@NeuralMiner)
- Update build-unix.md #1686 (@Quezacoatl1)
- Replace deprecated QT methods #1693 (@Pythonix)
- Made protocol.h more similar to bitcoin #1688 (@Pythonix)
- Touch up some details for block version 11 #1697 (@cyrossignol)
- More tweaks for block version 11 #1700 (@cyrossignol)
- Finish the conversion to the BCLog class based logger #1699 (@jamescowens)
- Move claim version transitional code in miner for proper signature #1712 (@cyrossignol)
- doc: Update threads in coding.txt #1730 (@div72)
- qt: Include QPainterPath in trafficgraphwidget.cpp #1733 (@div72)
- doc: Update doc/build-unix.md #1731 (@div72)
- gui: Show peers tab on connections icon click #1734 (@div72)
- refactor: Change return type of IsMine to isminetype && move wallet files to wallet directory #1722 (@div72)
- build: Updates boost to 1.73.0 for depends #1673 (@jamescowens)
- doc: Update Unit Test Readme #1743 (@RoboticMind)
- wallet: Change Assert To Error Message In kernel.cpp #1748 (@RoboticMind)
- scraper: Shorten display representation of verification codes #1754 (@cyrossignol)
- log: Change ".B." to Clear Message #1758 (@RoboticMind)
- util: Fix braindamage in GetDefaultDataDir() #1737 (@jamescowens)
- scraper: Improve scraper processing of beacon verifications #1760 (@jamescowens)
- scraper: Add instrumentation to convergencereport #1763 (@jamescowens)
- rpc: Improve rpc stress test script #1767 (@tunisiano187)
- Generalize enum serialization #1770 (@cyrossignol)
- scraper: Improve handling of ETags in http class and tweak verified beacon logic #1776 (@jamescowens)
- scraper: Improve ProcessNetworkWideFromProjectStats and other tweaks #1778 (@jamescowens)
- researcher: Automate beacon advertisement for renewals only #1781 (@cyrossignol)
- gui: Tweak behavior of beacon page in researcher wizard #1784 (@cyrossignol)
- Prepare for block version 11 hard-fork on testnet #1787 (@cyrossignol)
- scraper: Modify UpdateVerifiedBeaconsFromConsensus #1791 (@jamescowens)
- gui: Optimize OverviewPage::updateTransactions() #1794 (@jamescowens)
- ci: Adopt ci changes from Bitcoin #1795 (@div72)
- consensus: switch snapshot accrual calculation to integer arithmetic #1799 (@cyrossignol)
- voting: Overhaul the voting system #1809 (@cyrossignol)
- contract: Optimize contract replay after chain reorganization #1815 (@cyrossignol)
- contract: Reimplement transaction messages as contracts #1816 (@cyrossignol)
- staking: Sign claim contracts with coinstake transaction #1817 (@cyrossignol)
- gui: Change research wizard text #1820 (@div72)
- net: Update protocol version and clean up net messaging #1824 (@cyrossignol)
- rpc, wallet: Corrections to GetAmounts #1825 (@jamescowens)
- gui: Tweak some minor researcher wizard details #1830 (@cyrossignol)
- gui: Change GetEstimatedStakingFrequency text #1836 (@jamescowens)
- scraper: Scraper global statistics cache optimization #1837 (@jamescowens)
- doc: Update Vulnerability Response Process #1843 (@RoboticMind)
- scraper: Optimization of manifest and parts sharing between ConvergedScraperStatsCache, mapManifest, and mapParts #1851 (@jamescowens)
- consensus: Update Checkpoints #1855 (@barton2526)
- docs: Update docs to build off master #1856 (@barton2526)
- gui: Fix and improve GUI combo box styles #1858 (@cyrossignol)
- build: Tweak Gridcoin installer for Fern release #1863 (@jamescowens)
- Remove old research age checks (rebase #1365) #1572 (@cyrossignol)
- Remove PrimaryCPID check from diagnostics dialog #1586 (@cyrossignol)
- Remove missed label for PrimaryCPID from diagnostics #1588 (@cyrossignol)
- Remove legacy quorum messaging system (@neural network) #1589 (@cyrossignol)
- Remove old remnants of legacy smart contract experiments #1594 (@cyrossignol)
- Remove block nonce for version 11 #1622 (@cyrossignol)
- Delete obsolete contrib/Installer and Upgrader directories #1623 (@jamescowens)
- Remove redundant LoadAdminMessages() calls #1625 (@cyrossignol)
- Remove some legacy informational RPC commands #1658 (@cyrossignol)
- Remove informational magnitude field from binary claims #1661 (@cyrossignol)
- Remove fDebug3,4, and net and convert to BCLog::LogFlags #1663 (@jamescowens)
- Remove qt5.7.1 depends support build System #1665 (@iFoggz)
- Remove unused jQuery library #1679 (@cyrossignol)
- Remove unused NetworkTimer() function and global state #1701 (@cyrossignol)
- Refactor claim context objects into contracts #1704 (@cyrossignol)
- Clean old assets up #1718 (@div72)
- Remove legacy "rain" RPC (not by-project rain) #1742 (@cyrossignol)
- Temporarily disable voting system on testnet #1769 (@cyrossignol)
- gui: Remove legacy GUI transaction description for contracts #1772 (@cyrossignol)
- gui: Remove transaction fee setting #1780 (@cyrossignol)
- trivial: Cleanup unused legacy functions #1793 (@cyrossignol)
- mining, rpc: Remove kernel-diff-best and kernel-diff-sum #1796 (@jamescowens)
- refactor: Remove libs subdirectory #1802 (@div72)
- scraper: cleanup unused/unnecessary functions #1803 (@jamescowens)
- gui: Remove useless "Detach databases at shutdown" #1810 (@jamescowens)
- test: Remove testnet condition for standard transactions #1814 (@cyrossignol)
- consensus: Remove transitional testnet code #1854 (@cyrossignol)
- Fix "Owed" amount in output of "magnitude" RPC method #1569 (@cyrossignol)
- Add support for paths with special characters on Windows #1571 (@cyrossignol)
- Fix lingering peers.dat temp files and clean up remaining paths #1582 (@cyrossignol)
- Fix incorrect beacon length warning in GUI transaction list #1585 (@cyrossignol)
- Fix default config file line endings on Windows #1587 (@cyrossignol)
- Reenable Travis builds for MacOS #1591 (@jamescowens)
- Correct peer detail info background color #1593 (@jamescowens)
- Fix exception in debug3 mode #1598 (@cyrossignol)
- Fix deadlock in "getmininginfo" RPC function #1596 (@cyrossignol)
- Fix accuracy of statistics in "network" RPC output #1602 (@cyrossignol)
- Fix heights for quorum vote weight calculations #1604 (@cyrossignol)
- Fix deadlock in log archiver when rename fails #1607 (@cyrossignol)
- Fix a spurious segmentation fault during client load on Windows with fast CPUs #1608 (@jamescowens)
- Fix lock order debugging and potential deadlocks #1612 (@jamescowens)
- Add dependencies #1613 (@Scalextrix)
- Fix std namespace pollution #1617 (@denravonska)
- Add missing condition for newbie accrual computer #1618 (@cyrossignol)
- Track first reward blocks in research accounts #1619 (@cyrossignol)
- Fix lingering beacon warning after advertisement #1627 (@cyrossignol)
- Fix accrual calculation for new, zero-magnitude CPIDs #1636 (@cyrossignol)
- Fix diagnostics, add ETTS test, fix tooltipcolor, add missing lock, and add email=investor check #1647 (@jamescowens)
- Fix help message of two RPC methods #1656 (@div72)
- Fix legacy accrual for newbie with non-zero past reward #1667 (@cyrossignol)
- Fix GUI autostart on Windows for paths with wide characters #1670 (@cyrossignol)
- Qualify boost bind placeholders with their full namespace #1672 (@Ponce)
- Fix suffix when copying txids #1677 (@div72)
- Unnecessary if-statement removed #1685 (@Pythonix)
- Fix consolidatemsunspent Help Message #1687 (@Pythonix)
- Fix gettransaction help message #1691 (@Pythonix)
- Fix GetNewMint To Look for Stakes #1692 (@RoboticMind)
- Suppress deprecated copy warnings for Qt with GCC 9+ #1702 (@cyrossignol)
- Fix exclusion error on stats processing and misplaced ENDLOCK logging entry #1710 (@jamescowens)
- Removed unnecessary comparison #1708 (@Pythonix)
- Fixed typo #1707 (@Pythonix)
- Fix out-of-bounds exception for peers tab version slashes #1713 (@cyrossignol)
- Fix transition for v1 superblocks when reorganizing #1714 (@cyrossignol)
- Touch up transition to version 2 transactions #1715 (@cyrossignol)
- Avoid mutating transactions in ConnectBlock() #1716 (@cyrossignol)
- Skip beacon advertisement when already pending #1726 (@cyrossignol)
- Fix Windows cross-compilation in newer environments #1728 (@cyrossignol)
- Fix out-of-bounds access in IsMineInner() #1736 (@cyrossignol)
- Fix a couple of block version 11 issues #1738 (@cyrossignol)
- Fix null pointer dereference in GUI researcher model #1741 (@cyrossignol)
- accrual: Reset research accounts when rebuilding accrual snapshots #1745 (@cyrossignol)
- scraper: Correct update for verified beacons #1747 (@jamescowens)
- accrual: Refactor tally initialization for snapshot rebuild #1749 (@cyrossignol)
- rpc: Fix "cpid" field in "beaconconvergence" RPC output #1750 (@cyrossignol)
- accrual: Fix snapshot accrual superblock state transitions #1752 (@cyrossignol)
- scraper: Correct stale verified beacon logic #1753 (@jamescowens)
- rpc: Correct possible divide by zero in getblockstats #1755 (@jamescowens)
- gui: Fix issues with researcher wizard flow #1756 (@cyrossignol)
- wallet: Stop Error When Starting From Zero #1759 (@RoboticMind)
- Don't count empty email as explicit investor #1761 (@cyrossignol)
- accrual: Fix snapshot accrual superblock state transitions #1764 (@cyrossignol)
- rpc: Cleanup Help Message and Fix Typo #1771 (@RoboticMind)
- scraper: Fix scraper etag header case sensitivity #1773 (@cyrossignol)
- consensus: Use explicit time to check if superblock needed #1774 (@cyrossignol)
- gui: Fix scroll area dark theme styles #1785 (@cyrossignol)
- rpc, gui: Fix three divide by zero possibilities #1789 (@jamescowens)
- rpc: Fix balance pre-check in "rainbymagnitude" RPC #1792 (@cyrossignol)
- accrual: Fix outdated comment and correct grammar #1800 (@RoboticMind)
- gui: Fix stuck cursor on labels #1801 (@div72)
- beacon: Fix research wizard beacon renewal status #1805 (@cyrossignol)
- gui: Fix translations for port numbers #1818 (@cyrossignol)
- util: Create parent directory #1821 (@div72)
- mining: Fix coinstake/claim signature order #1828 (@cyrossignol)
- voting: Remove double increment in loop #1831 (@cyrossignol)
- neuralnet, scraper: Fix compilation with gcc5 and older libcurl #1832 (@a123b)
- wallet: Fix smallest coin selection for contracts #1841 (@cyrossignol)
- gui: Fix display of polls with no votes yet #1844 (@cyrossignol)
- gui: add indentation to diagnostic status bar labels #1849 (@jamescowens)
- voting, gui: Fix formatting and alignment of vote shares and percent #1850 (@jamescowens)
- wallet, rpc: Fix for self-transactions in listtransactions #1852 (@jamescowens)
- accrual: Clear any accrual snapshots when syncing from pre-v11 #1853 (@cyrossignol)
- accrual: Fix reset of accrual directory if starting sync below research age height #1857 (@jamescowens)
- gui: Fix researcher wizard layout on macOS with native theme #1860 (@cyrossignol)
Syscoin Platform’s Great Reddit Scaling Bake-off Proposal
| || | submitted by sidhujag to ethereum [link] [comments]
We are excited to participate and present Syscoin Platform's ideal characteristics and capabilities towards a well-rounded Reddit Community Points solution!
Our scaling solution for Reddit Community Points involves 2-way peg interoperability with Ethereum. This will provide a scalable token layer built specifically for speed and high volumes of simple value transfers at a very low cost, while providing sovereign ownership and onchain finality.
Token transfers scale by taking advantage of a globally sorting mempool that provides for probabilistically secure assumptions of “as good as settled”. The opportunity here for token receivers is to have an app-layer interactivity on the speed/security tradeoff (99.9999% assurance within 10 seconds). We call this Z-DAG, and it achieves high-throughput across a mesh network topology presently composed of about 2,000 geographically dispersed full-nodes. Similar to Bitcoin, however, these nodes are incentivized to run full-nodes for the benefit of network security, through a bonded validator scheme. These nodes do not participate in the consensus of transactions or block validation any differently than other nodes and therefore do not degrade the security model of Bitcoin’s validate first then trust,
across every node. Each token transfer settles on-chain. The protocol follows Bitcoin core policies so it has adequate code coverage and protocol hardening to be qualified as production quality software. It shares a significant portion of Bitcoin’s own hashpower through merged-mining
This platform as a whole can serve token microtransactions, larger settlements, and store-of-value in an ideal fashion, providing probabilistic scalability whilst remaining decentralized according to Bitcoin design. It is accessible to ERC-20 via a permissionless and trust-minimized bridge that works in both directions. The bridge and token platform are currently available on the Syscoin mainnet. This has been gaining recent attention
for use by loyalty point programs and stablecoins such as Binance USD.
Syscoin Foundation identified a few paths for Reddit to leverage this infrastructure, each with trade-offs. The first provides the most cost-savings and scaling benefits at some sacrifice of token autonomy. The second offers more preservation of autonomy with a more narrow scope of cost savings than the first option, but savings even so. The third introduces more complexity than the previous two yet provides the most overall benefits. We consider the third as most viable as it enables Reddit to benefit even while retaining existing smart contract functionality. We will focus on the third option, and include the first two for good measure.
- Distribution, burns and user-to-user transfers of Reddit Points are entirely carried out on the Syscoin network. This full-on approach to utilizing the Syscoin network provides the most scalability and transaction cost benefits of these scenarios. The tradeoff here is distribution and subscription handling likely migrating away from smart contracts into the application layer.
- The Reddit Community Points ecosystem can continue to use existing smart contracts as they are used today on the Ethereum mainchain. Users migrate a portion of their tokens to Syscoin, the scaling network, to gain much lower fees, scalability, and a proven base layer, without sacrificing sovereign ownership. They would use Syscoin for user-to-user transfers. Tips redeemable in ten seconds or less, a high-throughput relay network, and onchain settlement at a block target of 60 seconds.
- Integration between Matic Network and Syscoin Platform - similar to Syscoin’s current integration with Ethereum - will provide Reddit Community Points with EVM scalability (including the Memberships ERC777 operator) on the Matic side, and performant simple value transfers, robust decentralized security, and sovereign store-of-value on the Syscoin side. It’s “the best of both worlds”. The trade-off is more complex interoperability.
Syscoin + Matic Integration Matic
and Blockchain Foundry Inc
, the public company formed by the founders of Syscoin
, recently entered a partnership
for joint research and business development initiatives. This is ideal for all parties as Matic Network and Syscoin Platform provide complementary utility. Syscoin offers characteristics for sovereign ownership and security based on Bitcoin’s time-tested model, and shares a significant portion of Bitcoin’s own hashpower. Syscoin’s focus is on secure and scalable simple value transfers, trust-minimized interoperability, and opt-in regulatory compliance for tokenized assets rather than scalability for smart contract execution. On the other hand, Matic Network can provide scalable EVM for smart contract execution. Reddit Community Points can benefit from both.
Syscoin + Matic integration is actively being explored by both teams, as it is helpful to Reddit, Ethereum, and the industry as a whole.
Proving Performance & Cost Savings
Our POC focuses on 100,000 on-chain settlements of token transfers on the Syscoin Core blockchain. Transfers and burns perform equally with Syscoin. For POCs related to smart contracts (subscriptions, etc), refer to the Matic Network proposal. On-chain settlement of 100k transactions was accomplished within roughly twelve minutes
, well-exceeding Reddit’s expectation of five days. This was performed using six full-nodes operating on compute-optimized AWS c4.2xlarge instances which were geographically distributed (Virginia, London, Sao Paulo Brazil, Oregon, Singapore, Germany). A higher quantity of settlements could be reached within the same time-frame with more broadcasting nodes involved, or using hosts with more resources for faster execution of the process.
Addresses used: 100,014
The demonstration was executed using this tool
. The results can be seen in the following blocks:
It is important to note that this POC is not focused on Z-DAG. The performance of Z-DAG has been benchmarked within realistic network conditions: Whiteblock’s audit
is publicly available. Network latency tests showed an average TPS around 15k with burst capacity up to 61k. Zero-latency control group exhibited ~150k TPS. Mainnet testing of the Z-DAG network is achievable and will require further coordination and additional resources.
Even further optimizations are expected in the upcoming Syscoin Core release which will implement a UTXO model for our token layer bringing further efficiency as well as open the door to additional scaling technology currently under research by our team and academic partners. At present our token layer is account-based, similar to Ethereum. Opt-in compliance structures will also be introduced soon which will offer some positive performance characteristics as well. It makes the most sense to implement these optimizations before performing another benchmark for Z-DAG, especially on the mainnet considering the resources required to stress-test this network.
Cost Savings Total cost for these 100k transactions: $0.63 USD
See the live fee comparison
for savings estimation between transactions on Ethereum and Syscoin. Below is a snapshot at time of writing:
ETH price: $318.55 ETH gas price: 55.00 Gwei ($0.37)
Syscoin price: $0.11 Snapshot of live fee comparison chart
Z-DAG provides a more efficient fee-market. A typical Z-DAG transaction costs 0.0000582 SYS.
Tokens can be safely redeemed/re-spent within seconds or allowed to settle on-chain beforehand. The costs should remain about this low for microtransactions.
Syscoin will achieve further reduction of fees and even greater scalability with offchain payment channels for assets, with Z-DAG as a resilience fallback. New payment channel technology is one of the topics under research by the Syscoin development team with our academic partners at TU Delft. In line with the calculation in the Lightning Networks white paper, payment channels using assets with Syscoin Core will bring theoretical capacity for each person on Earth (7.8 billion) to have five on-chain transactions per year, per person, without requiring anyone to enter a fee market (aka “wait for a block”). This exceeds the minimum LN expectation of two transactions per person, per year; one to exist on-chain and one to settle aggregated value.
Tools, Infrastructure & Documentation
Syscoin Bridge Mainnet Demonstration of Syscoin Bridge with the Basic Attention Token ERC-20
A two-way blockchain interoperability system that uses Simple Payment Verification to enable:
- Any Standard ERC-20 token to be moved from Ethereum to the Syscoin blockchain as a Syscoin Platform Token (SPT), and back to Ethereum
- Any SPT to be moved from Syscoin to the Ethereum blockchain as an ERC-20 token, and back to Syscoin
- No counterparties involved
- No trading mechanisms involved
- No third-party liquidity providers required
- Cross-chain Fractional Supply - 2-way peg - Token supply maintained globally
- ERC-20s gain vastly improved transactionality with the Syscoin Token Platform, along with the security of bitcoin-core-compliant PoW.
- SPTs gain access to all the tooling, applications and capabilities of Ethereum for ERC-20, including smart contracts.
Source code https://github.com/syscoin/?q=sysethereum
Tools to simplify using Syscoin Bridge as a service with dapps and wallets will be released some time after implementation of Syscoin Core 4.2. These will be based upon the same processes which are automated in the current live Sysethereum Dapp
that is functioning with the Syscoin mainnet.
Documentation Syscoin Bridge & How it Works
(description and process flow) Superblock Validation Battles HOWTO: Provision the Bridge for your ERC-20 HOWTO: Setup an Agent Developer & User Diligence
The Syscoin Ethereum Bridge is secured by Agent nodes participating in a decentralized and incentivized model that involves roles of Superblock challengers and submitters. This model is open to participation. The benefits here are trust-minimization, permissionless-ness, and potentially less legal/regulatory red-tape than interop mechanisms that involve liquidity providers and/or trading mechanisms.
The trade-off is that due to the decentralized nature there are cross-chain settlement times of one hour to cross from Ethereum to Syscoin, and three hours to cross from Syscoin to Ethereum. We are exploring ways to reduce this time while maintaining decentralization via zkp. Even so, an “instant bridge” experience could be provided by means of a third-party liquidity mechanism. That option exists but is not required for bridge functionality today. Typically bridges are used with batch value, not with high frequencies of smaller values, and generally it is advantageous to keep some value on both chains for maximum availability of utility. Even so, the cross-chain settlement time is good to mention here.
Cost Ethereum -> Syscoin
: Matic or Ethereum transaction fee for bridge contract interaction, negligible Syscoin transaction fee for minting tokens Syscoin -> Ethereum:
Negligible Syscoin transaction fee for burning tokens, 0.01% transaction fee paid to Bridge Agent in the form of the ERC-20, Matic or Ethereum transaction fee for contract interaction.
Zero-Confirmation Directed Acyclic Graph is an instant settlement protocol that is used as a complementary system to proof-of-work (PoW) in the confirmation of Syscoin service transactions. In essence, a Z-DAG is simply a directed acyclic graph (DAG) where validating nodes verify the sequential ordering of transactions that are received in their memory pools. Z-DAG is used by the validating nodes across the network to ensure that there is absolute consensus on the ordering of transactions and no balances are overflowed (no double-spends).
- Unique fee-market that is more efficient for microtransaction redemption and settlement
- Uses decentralized means to enable tokens with value transfer scalability that is comparable or exceeds that of credit card networks
- Provides high throughput and secure fulfillment even if blocks are full
- Probabilistic and interactive
- 99.9999% security assurance within 10 seconds
- Can serve payment channels as a resilience fallback that is faster and lower-cost than falling-back directly to a blockchain
- Each Z-DAG transaction also settles onchain through Syscoin Core at 60-second block target using SHA-256 Proof of Work consensus
Source code https://github.com/syscoin/syscoin
provides tooling for all Syscoin Core RPCs including interactivity with Z-DAG.
Documentation Z-DAG White Paper
Useful read: An in-depth Z-DAG discussion between Syscoin Core developer Jag Sidhu and Brave Software Research Engineer Gonçalo Pestana
Z-DAG enables the ideal speed/security tradeoff to be determined per use-case in the application layer. It minimizes the sacrifice required to accept and redeem fast transfers/payments while providing more-than-ample security for microtransactions. This is supported on the premise that a Reddit user receiving points does need security yet generally doesn’t want nor need to wait for the same level of security as a nation-state settling an international trade debt. In any case, each Z-DAG transaction settles onchain at a block target of 60 seconds.
Syscoin Specs Syscoin 3.0 White Paper
(4.0 white paper is pending. For improved scalability and less blockchain bloat, some features of v3 no longer exist in current v4: Specifically Marketplace Offers, Aliases, Escrow, Certificates, Pruning, Encrypted Messaging)
- 16MB block bandwidth per minute assuming segwit witness carrying transactions, and transactions ~200 bytes on average
- SHA256 merge mined with Bitcoin
- UTXO asset layer, with base Syscoin layer sharing identical security policies as Bitcoin Core
- Z-DAG on asset layer, bridge to Ethereum on asset layer
- On-chain scaling with prospect of enabling enterprise grade reliable trustless payment processing with on/offchain hybrid solution
- Focus only on Simple Value Transfers. MVP of blockchain consensus footprint is balances and ownership of them. Everything else can reduce data availability in exchange for scale (Ethereum 2.0 model). We leave that to other designs, we focus on transfers.
- Future integrations of MAST/Taproot to get more complex value transfers without trading off trustlessness or decentralization.
- Zero-knowledge Proofs are a cryptographic new frontier. We are dabbling here to generalize the concept of bridging and also verify the state of a chain efficiently. We also apply it in our Digital Identity projects at Blockchain Foundry (a publicly traded company which develops Syscoin softwares for clients). We are also looking to integrate privacy preserving payment channels for off-chain payments through zkSNARK hub & spoke design which does not suffer from the HTLC attack vectors evident on LN. Much of the issues plaguing Lightning Network can be resolved using a zkSNARK design whilst also providing the ability to do a multi-asset payment channel system. Currently we found a showstopper attack (American Call Option) on LN if we were to use multiple-assets. This would not exist in a system such as this.
Web3 and mobile wallets are under active development by Blockchain Foundry Inc as WebAssembly applications and expected for release not long after mainnet deployment of Syscoin Core 4.2. Both of these will be multi-coin wallets that support Syscoin, SPTs, Ethereum, and ERC-20 tokens. The Web3 wallet will provide functionality similar to Metamask.
Syscoin Platform and tokens are already integrated with Blockbook. Custom hardware wallet support currently exists via ElectrumSys
. First-class HW wallet integration through apps such as Ledger Live will exist after 4.2. Current supported wallets Syscoin Spark Desktop Syscoin-Qt
Thank you for close consideration of our proposal. We look forward to feedback, and to working with the Reddit community to implement an ideal solution using Syscoin Platform!
The White Dragon : A Canadian Dragon Portfolio
submitted by ChudBuntsman to pmstocks [link] [comments]
Alright guys, Ive been working on this for a while and a post on here by a guy describing his portfolio here was the final kick in the ass for me to put this together. I started writing this to summarize what Im doing for my friends who are beginners, and also for me to make some sense of it for myself
Hopefully parts of it are useful to you, and also ideally you guys can point out errors or have a suggestion or two. I'm posting this here as opposed to investing
(blech) because they're just gonna tell me to buy an index fund.
This first section is a preamble describing the Canadian tax situation and why Im doing things the way that I am. Feel free to skip it if you dont care about that. Also, there might be mistake regarding what the laws are here so dont take my word for it and verify it for yourself please.
So here in Canada we have two types of registered accounts (theres actually more but whatver). There is the TFSA "Tax Free Savings Account", and RRSP "Registered Retirement Savings Account"
For the sake of simplicity, from the time you turn 18 you are allowed to deposit 5k (it changes year to year based on inflation etc)in each of them. That "room" accumulates retroactively, so if you haventdone anything and are starting today and you are 30 you have around 60k you can put in each of them. The prevailing wisdom is that you should max out the TFSA first and you'll see why in a minute.
TFSA is post tax deposits, with no capital gains or other taxes applied to selling your securities, dividends or anything else. You can withdraw your gains at any time, and the amount that you withdraw is added to the "room" you have for the next year. So lets say I maxed out my TFSA contributions and I take out 20k today, on January of next year I can put back in 20k plus the 5 or whatever they allow for that year. You can see how powerful this is. Theres a few limitations on what is eligable to be held in the TFSA such as bitcoin/bitcoin ETFs, overseas stocks that arent listed on NYSE, TSX, london and a few others. You can Buy to Open and Sell to Close call and put options as well as write Covered Calls.
The RRSP is pre-tax deposits and is a tax deferred scheme. You deposit to lower your income tax burden (and hopefully drop below a bracket) but once you retire you will be taxed on anything you pull out. Withdrawing early has huge penalties and isnt recommended. You are however allowed to borrow against it for a down payment as a first time home buyer. The strategy with these is that a youngperson entering the workforce is likely to be in a fairly low tax bracket and (hopefully) earns more money as they get older and more skilled so the RRSP has more value the greater your pre-taxincome is. You can also do this Self Directed. Its not relevant to this strategy but I included it for the sake of context.
Non registered accounts ( or any other situation, such as selling commercial real estate etc) is subject to a capital gains tax. In so far as I understand it, you add all your gains and losses up at the end of the year. If its a positive number, you cut that number IN HALF and add it to your regular pre-tax income. So if I made 60k from the dayjob and 20k on my margin account that adds up to 70k that I get taxed on. if its a loss, you carry that forward into the next year. Theres no distinction between long term and short term. Also physical PMs are treated differently and I'll fill that part in later once I have the details down.
The reason why all that babble is important is that my broker Questrade, which isnt as good as IB (the only real other option up here as far as Im aware) has one amazing feature that no other broker has: "Margin Power"
If you have a TFSA and a Margin account with them, you can link them together and have your securities in the TFSA collateralise your Margin account. Essentially, when it comes to the Maintenance Excess of the Margin Account QT doesnt care if its in the TFSA *or* the Margin!
You can see how powerful this is.
So as you can tell by the title, a lot of this is heavily inspired by Chris Cole's paper "The Allegory of the Hawk and the Serpent". You can read it here: https://www.artemiscm.com/welcome#research
Between it, his interviews and my mediocre options skills at the time my mind was blown. Unfortunately I didnt know how to do the Long Volatility part until after the crash in March but I've since then had nothing but time to scour the internet and learn as much as I could.
The way I interpret this isnt necessarily "what you should have right now", but what abstracted model they were able to backtest that gave them the best performance over the 90 years. Also, a lot of my portfolio I already had before I started trying to build this.
As such my allocations dont match the proportions he gave. Not saying my allocations are better, just showing where they are at this time.
I'm going to describe how I do Long Volatility at the end rather than the beginning since the way *I* do it wont make sense until you see the rest of the portflio.
Physical PMs 22%
I'm not sure wether he intended this to be straight up physical gold or include miners and royalty streaming companies so I will just keep this as physical.
I consider Silver to be a non-expiring call option on gold, so that can live here too. I am actually *very* overweight silver and my strategy is to convert a large portion of it to gold (mostly my bars) to gold as the ratio tightens up.
If youre into crypto, you can arguably say that has a place in this section.
If an ETF makes sense for part of your portfolio, I suggest the Sprott ones such as PHYS. Sprott is an honest business and they actually have the metal they say they have. If you have enough, you can redeem your shares from the Royal Canadian Mint. The only downside is that they dont have an options chain, so you cant sell covered calls etc. Simple enough I suppose.
One thing to bear in mind, there is a double edged sword with this class of assets. They're out of the system, theyre nobody's business but your own and theres no counter party. That unfortunately means that you cant lever against it for margin or sell covered calls etc. You can still buy puts though (more on that later)
Commodity Trend (CTA) 10% https://youtu.be/tac8sWPZW0w
Patrick Ceresna gave a good presentation on what this strategy is. Until I watched this video I just thought it meant "buy commodities". A real CTA does this with futures also so aside from the way he showed, there are two other ETFs that are worth looking at.
COM - This is an explicit trend following ETF that follows a LONG/FLAT strategy instead of LONG/SHORT on a pile of commodity futures. So if they get a "sell" signal for oil or soybeans they sell what they have and go to cash.
COMT- Holds an assortment of different month futures in different commodities, as well as a *lot* of various related shares in producers. Its almost a one stop shop commodities portfolio. Pays a respectable dividend in December
If you want to break the "rules" of CTA, and include equities theres a few others that are also worth looking at
KOL- This is a coal ETF. The problems with it are that a lot of the holdings dont have much to do with coal. One of them is a tractor company. A lot of the companies are Chinese so theres a bit of a red flag.
Obviously Thermal Coal, the kind used for heating and powerplants isnt in vogue and wont be moving forward...but coking coal is used for steel manufacturing and that ain't going anywhere. The dividend is huge, pays out in December. A very very small position might be worth the risk.
Uranium- I'm in URA because thats the only way for me to get exposure to Kazatoprom (#1 producer), which is 20% of the holdings. The other 20% is Cameco (#2 producer)and then its random stuff.
Other than that I have shares in Denison which seems like its a good business with some interesting projects underway. I'm still studying the uranium space so I dont really have much to say about it of any value.
RSX- Russia large caps. If you dont want to pick between the myriad of undervalued, high dividend paying commodity companies that Russia has then just grab this. It only pays in December but it has a liquid options chain so you can do Covered Calls in the meantime if you want.
NTR- Nutrien, canadian company that was formed when two others merged. They are now the worlds largest potash producer. Pretty good dividend. They have some financial difficulties and the stocks been in a downtrend forever. I feel its a good candidate to watch or sell some puts on.
I'm trying to come up with a way to play agriculture since this new phase we're going to be entering is likely to cause huge food shortages.
EURN and NAT- I got in fairly early on the Tanker hype before it was even hype as a way to short oil but I got greedy and lost a lot of my gains. I pared down my position and I'm staying for the dividend.
If you get an oil sell signal, this might be a way to play that still.
Fixed Income/Bonds 10%
Now, I am not a bond expert but unless youre doing some wacky spreads with futures or whatever... I dont see much reason to buy government debt any more. If you are, youre basically betting that they take rates negative. Raoul Pal of Real Vision is pretty firm in his conviction that this will happen. I know better than to argue with him but I dont see risk/reward as being of much value.
HOWEVER, I found two interesting ETFs that seem to bring something to this portfolio
IVOL- This is run by Nancy Davis, and is comprised of TIPS bonds which are nominally inflation protected (doubt its real inflation but whatever) overlayed with some OTC options that are designed to pay off big if the Fed loses control of the long end of the yield curve, which is what might happen during a real inflation situation. Pays out a decent yield monthly
TAIL- This is a simpler portfolio of 10yr treasuries with ladder of puts on the SPX. Pays quarterly.
Equities 58% (shared with options/volatility below)
This is where it gets interesting, obviously most of this is in mining shares but before I get to those I found some interesting stuff that I'm intending to build up as I pare down my miners when the time comes to start doing that.
VIRT- I cant remember where I saw this, but people were talking about this as a volatility play. Its not perfect, but look at the chart compared to SPY. Its a HFT/market making operation, the wackier things get the more pennies they can scalp. A 4% dividend isnt shabby either.
FUND- This is an interesting closed end fund run by Whitney George, one of the principals at Sprott. He took it with him when he joined the company. Ive read his reports and interviews and I really like his approach to value and investing. He's kind of like if Warren Buffett was a gold bug. Theres 120 holdings in there, mostly small caps and very diverse...chicken factories, ball bearings all kinds of boring ass shit that nobody knows exists. Whats crucial is that most of it "needs to exist". Between him, his family and other people at Sprott they control 40% or so of the shares, so they definitely have skin in the game. Generous dividend.
ZIG- This is a "deep value" strategy fund, run by Tobias Carlisle. He has a fairly simple valuation formula called the Acquirer's Multiple that when he backtested it, is supposed to perform very well. He did an interview with Chris Cole on real Vision where he discusses how Value and Deep Value havent done well recently, but over the last 100 years have proven to be very viable strategies. If we feel that theres a new cycle brewing, then this strategy may work again moving forward.
I want to pause and point out something here, Chris Cole, Nassim Taleb and the guys at Mutiny Fund spend a lot of effort explaining that building a portfolio is a lot like putting together a good basketall team. They need to work together, and pick up each others slack
A lot of the ETFs I'm listing here are in many ways portfolios in and of themselves and are *actively managed*. I specifically chose them because they follow a methodology that I respect but I can't do myself because I dont have the skill, temperament or access to.
The next one is a hidden gem and ties into this. I'm not sure how much more upside there is in this one but man was I surprised.
SII- Sprott Inc. I *never* see people listing this stock in their PMs portfolios. A newsletter I'm subscribed to described this stock as the safest way to play junior miners. Their industry presence, intellectual capital and connections means that they get *the best* private placement deals in the best opportunities. I cant compete with a staff like theirs and I'm not going to try. I bought this at 2.50, and I liked the dividend. Since then they did a reverse split to get on the NYSE and like the day after the stock soared.
When it comes to mining ETFS I like GOAU and SILJ the best. None of their major holdings are dead weight companies that are only there because of market cap. I dont want Barrick in my portfolio etc.
SGDJ is a neat version of GDXJ.
Aside from that my individual miners/royalty companies are (no particular order)
RIO- Rio2 on the tsx, not rio tinto
KL Options/Volatility: varies
So this is where we get to the part about options, Volatility and how I do it. I started out in the options space with The Wheel strategy and the Tastytrade approach of selling premium. The spreads and puts I sell, are on shares listed above, in fact some of those I dont hold anymore.
Theres tons of stuff on this in thetagang
so I wont go into a whole bunch (and you shouldnt be learning the mechanics from me anyway) but theres one thing I want to go over before it gets wild.
If I sell a Cash Secured Put, from a risk management perspective its identical to just buying 100 shares of the underlying security. You are equally "Short Vol" as well, it just that with options
its a little more explicit with the Greeks and everything. But if I use my margin that I was talking about earlier, then I can still collect the premium and the interest doesnt kick in unless Im actually assigned the shares.
But if I sell too many puts on KL or AG, and something happens where the miners get cut down (and lets be real, they all move together) my margin goes down and then I get assigned and kaboom...my account gets blown up
So what I need to do, is balance out the huge Short Vol situation in my portfolio, be net Long Vol and directly hedge my positions. Since the overwhelming majority of my equities are all tied to bullion this is actually a very easy thing to do.
Backspreads https://youtu.be/pvX5_rkm5x0 https://youtu.be/-jTvWOGVsK8 https://youtu.be/muYjjm934iY
So I set this up so the vast majority of my margin is tied up in these 1-2 or even 1-3 ratio put spreads that *I actually put on for a small credit*, and roll them every once in a while. I run them on SLV, and GDX.
I keep enough room on my margin so I can withstand a 10% drawdown before it sets off the long end of the spreads and then I can ride it out until it turns around and we keep the PM bull market going.
Theres another cool spread I've been using, which is a modified Jade Lizard; if already hold shares, I'll sell a put, sell a covered call, and use some of the premium to buy a longer dated call. Ive been running this on AG mostly.
I have a few more spreads I can show you but Im tired now so it'll have to wait for later.
As I said multiple times, I do intend to trim these miners later but now isnt the time for that IMO. I'm also monitoring this almost full time since I have an injury and have nothing better to do until I heal :p
Groestlcoin 6th Anniversary Release
submitted by Yokomoko_Saleen to groestlcoin [link] [comments]
Dear Groestlers, it goes without saying that 2020 has been a difficult time for millions of people worldwide. The groestlcoin team would like to take this opportunity to wish everyone our best to everyone coping with the direct and indirect effects of COVID-19. Let it bring out the best in us all and show that collectively, we can conquer anything.
The centralised banks and our national governments are facing unprecedented times with interest rates worldwide dropping to record lows in places. Rest assured that this can only strengthen the fundamentals of all decentralised cryptocurrencies and the vision that was seeded with Satoshi's Bitcoin whitepaper over 10 years ago. Despite everything that has been thrown at us this year, the show must go on and the team will still progress and advance to continue the momentum that we have developed over the past 6 years.
In addition to this, we'd like to remind you all that this is Groestlcoin's 6th Birthday release! In terms of price there have been some crazy highs and lows over the years (with highs of around $2.60 and lows of $0.000077!), but in terms of value– Groestlcoin just keeps getting more valuable! In these uncertain times, one thing remains clear – Groestlcoin will keep going and keep innovating regardless. On with what has been worked on and completed over the past few months.
UPDATED - Groestlcoin Core 2.18.2
This is a major release of Groestlcoin Core with many protocol level improvements and code optimizations, featuring the technical equivalent of Bitcoin v0.18.2 but with Groestlcoin-specific patches. On a general level, most of what is new is a new 'Groestlcoin-wallet' tool which is now distributed alongside Groestlcoin Core's other executables. NOTE: The 'Account' API has been removed from this version which was typically used in some tip bots. Please ensure you check the release notes from 2.17.2 for details on replacing this functionality.
- Builds are now done through Gitian
- Calls to getblocktemplate will fail if the segwit rule is not specified. Calling getblocktemplate without segwit specified is almost certainly a misconfiguration since doing so results in lower rewards for the miner. Failed calls will produce an error message describing how to enable the segwit rule.
- A warning is printed if an unrecognized section name is used in the configuration file. Recognized sections are [test], [main], and [regtest].
- Four new options are available for configuring the maximum number of messages that ZMQ will queue in memory (the "high water mark") before dropping additional messages. The default value is 1,000, the same as was used for previous releases.
- The rpcallowip option can no longer be used to automatically listen on all network interfaces. Instead, the rpcbind parameter must be used to specify the IP addresses to listen on. Listening for RPC commands over a public network connection is insecure and should be disabled, so a warning is now printed if a user selects such a configuration. If you need to expose RPC in order to use a tool like Docker, ensure you only bind RPC to your localhost, e.g. docker run [...] -p 127.0.0.1:1441:1441 (this is an extra :1441 over the normal Docker port specification).
- The rpcpassword option now causes a startup error if the password set in the configuration file contains a hash character (#), as it's ambiguous whether the hash character is meant for the password or as a comment.
- The whitelistforcerelay option is used to relay transactions from whitelisted peers even when not accepted to the mempool. This option now defaults to being off, so that changes in policy and disconnect/ban behavior will not cause a node that is whitelisting another to be dropped by peers.
- A new short about the JSON-RPC interface describes cases where the results of anRPC might contain inconsistencies between data sourced from differentsubsystems, such as wallet state and mempool state.
- A new document (https://github.com/groestlcoin/groestlcoin/blob/mastedoc/groestlcoin-conf.md) about the groestlcoin.conf file describes how to use it to configure Groestlcoin Core.
- A new document introduces Groestlcoin Core's BIP174 interface, which is used to allow multiple programs to collaboratively work to create, sign, and broadcast new transactions. This is useful for offline (cold storage) wallets, multisig wallets, coinjoin implementations, and many other cases where two or more programs need to interact to generate a complete transaction.
- The output script descriptor (https://github.com/groestlcoin/groestlcoin/blob/mastedoc/descriptors.md) documentation has been updated with information about new features in this still-developing language for describing the output scripts that a wallet or other program wants to receive notifications for, such as which addresses it wants to know received payments. The language is currently used in multiple new and updated RPCs described in these release notes and is expected to be adapted to other RPCs and to the underlying wallet structure.
- A new --disable-bip70 option may be passed to ./configure to prevent Groestlcoin-Qt from being built with support for the BIP70 payment protocol or from linking libssl. As the payment protocol has exposed Groestlcoin Core to libssl vulnerabilities in the past, builders who don't need BIP70 support are encouraged to use this option to reduce their exposure to future vulnerabilities.
- The minimum required version of Qt (when building the GUI) has been increased from 5.2 to 5.5.1 (the depends system provides 5.9.7)
- getnodeaddresses returns peer addresses known to this node. It may be used to find nodes to connect to without using a DNS seeder.
- listwalletdir returns a list of wallets in the wallet directory (either the default wallet directory or the directory configured bythe -walletdir parameter).
- getrpcinfo returns runtime details of the RPC server. Currently, it returns an array of the currently active commands and how long they've been running.
- deriveaddresses returns one or more addresses corresponding to an output descriptor.
- getdescriptorinfo accepts a descriptor and returns information aboutit, including its computed checksum.
- joinpsbts merges multiple distinct PSBTs into a single PSBT. The multiple PSBTs must have different inputs. The resulting PSBT will contain every input and output from all the PSBTs. Any signatures provided in any of the PSBTs will be dropped.
- analyzepsbt examines a PSBT and provides information about what the PSBT contains and the next steps that need to be taken in order to complete the transaction. For each input of a PSBT, analyze psbt provides information about what information is missing for that input, including whether a UTXO needs to be provided, what pubkeys still need to be provided, which scripts need to be provided, and what signatures are still needed. Every input will also list which role is needed to complete that input, and analyzepsbt will also list the next role in general needed to complete the PSBT. analyzepsbt will also provide the estimated fee rate and estimated virtual size of the completed transaction if it has enough information to do so.
- utxoupdatepsbt searches the set of Unspent Transaction Outputs (UTXOs) to find the outputs being spent by the partial transaction. PSBTs need to have the UTXOs being spent to be provided because the signing algorithm requires information from the UTXO being spent. For segwit inputs, only the UTXO itself is necessary. For non-segwit outputs, the entire previous transaction is needed so that signers can be sure that they are signing the correct thing. Unfortunately, because the UTXO set only contains UTXOs and not full transactions, utxoupdatepsbt will only add the UTXO for segwit inputs.
- getpeerinfo now returns an additional minfeefilter field set to the peer's BIP133 fee filter. You can use this to detect that you have peers that are willing to accept transactions below the default minimum relay fee.
- The mempool RPCs, such as getrawmempool with verbose=true, now return an additional "bip125-replaceable" value indicating whether thetransaction (or its unconfirmed ancestors) opts-in to asking nodes and miners to replace it with a higher-feerate transaction spending any of the same inputs.
- settxfee previously silently ignored attempts to set the fee below the allowed minimums. It now prints a warning. The special value of"0" may still be used to request the minimum value.
- getaddressinfo now provides an ischange field indicating whether the wallet used the address in a change output.
- importmulti has been updated to support P2WSH, P2WPKH, P2SH-P2WPKH, and P2SH-P2WSH. Requests for P2WSH and P2SH-P2WSH accept an additional witnessscript parameter.
- importmulti now returns an additional warnings field for each request with an array of strings explaining when fields are being ignored or are inconsistent, if there are any.
- getaddressinfo now returns an additional solvable Boolean field when Groestlcoin Core knows enough about the address's scriptPubKey, optional redeemScript, and optional witnessScript for the wallet to be able to generate an unsigned input spending funds sent to that address.
- The getaddressinfo, listunspent, and scantxoutset RPCs now return an additional desc field that contains an output descriptor containing all key paths and signing information for the address (except for the private key). The desc field is only returned for getaddressinfo and listunspent when the address is solvable.
- importprivkey will preserve previously-set labels for addresses or public keys corresponding to the private key being imported. For example, if you imported a watch-only address with the label "coldwallet" in earlier releases of Groestlcoin Core, subsequently importing the private key would default to resetting the address's label to the default empty-string label (""). In this release, the previous label of "cold wallet" will be retained. If you optionally specify any label besides the default when calling importprivkey, the new label will be applied to the address.
- getmininginfo now omits currentblockweight and currentblocktx when a block was never assembled via RPC on this node.
- The getrawtransaction RPC & REST endpoints no longer check the unspent UTXO set for a transaction. The remaining behaviors are as follows:
- If a blockhash is provided, check the corresponding block.
- If no blockhash is provided, check the mempool.
- If no blockhash is provided but txindex is enabled, also check txindex.
- unloadwallet is now synchronous, meaning it will not return until the wallet is fully unloaded.
- importmulti now supports importing of addresses from descriptors. A desc parameter can be provided instead of the "scriptPubKey" in are quest, as well as an optional range for ranged descriptors to specify the start and end of the range to import. Descriptors with key origin information imported through importmulti will have their key origin information stored in the wallet for use with creating PSBTs.
- listunspent has been modified so that it also returns witnessScript, the witness script in the case of a P2WSH orP2SH-P2WSH output.
- createwallet now has an optional blank argument that can be used to create a blank wallet. Blank wallets do not have any keys or HDseed. They cannot be opened in software older than 2.18.2. Once a blank wallet has a HD seed set (by using sethdseed) or private keys, scripts, addresses, and other watch only things have been imported, the wallet is no longer blank and can be opened in 2.17.2. Encrypting a blank wallet will also set a HD seed for it.
- signrawtransaction is removed after being deprecated and hidden behind a special configuration option in version 2.17.2.
- The 'account' API is removed after being deprecated in v2.17.2 The 'label' API was introduced in v2.17.2 as a replacement for accounts. See the release notes from v2.17.2 for a full description of the changes from the 'account' API to the 'label' API.
- addwitnessaddress is removed after being deprecated in version 2.16.0.
- generate is deprecated and will be fully removed in a subsequent major version. This RPC is only used for testing, but its implementation reached across multiple subsystems (wallet and mining), so it is being deprecated to simplify the wallet-node interface. Projects that are using generate for testing purposes should transition to using the generatetoaddress RPC, which does not require or use the wallet component. Calling generatetoaddress with an address returned by the getnewaddress RPC gives the same functionality as the old generate RPC. To continue using generate in this version, restart groestlcoind with the -deprecatedrpc=generate configuration option.
- Be reminded that parts of the validateaddress command have been deprecated and moved to getaddressinfo. The following deprecated fields have moved to getaddressinfo: ismine, iswatchonly,script, hex, pubkeys, sigsrequired, pubkey, embedded,iscompressed, label, timestamp, hdkeypath, hdmasterkeyid.
- The addresses field has been removed from the validateaddressand getaddressinfo RPC methods. This field was confusing since it referred to public keys using their P2PKH address. Clients should use the embedded.address field for P2SH or P2WSH wrapped addresses, and pubkeys for inspecting multisig participants.
- A new /rest/blockhashbyheight/ endpoint is added for fetching the hash of the block in the current best blockchain based on its height (how many blocks it is after the Genesis Block).
- A new Window menu is added alongside the existing File, Settings, and Help menus. Several items from the other menus that opened new windows have been moved to this new Window menu.
- In the Send tab, the checkbox for "pay only the required fee" has been removed. Instead, the user can simply decrease the value in the Custom Fee rate field all the way down to the node's configured minimumrelay fee.
- In the Overview tab, the watch-only balance will be the only balance shown if the wallet was created using the createwallet RPC and thedisable_private_keys parameter was set to true.
- The launch-on-startup option is no longer available on macOS if compiled with macosx min version greater than 10.11 (useCXXFLAGS="-mmacosx-version-min=10.11" CFLAGS="-mmacosx-version-min=10.11" for setting the deployment sdkversion)
- A new groestlcoin-wallet tool is now distributed alongside Groestlcoin Core's other executables. Without needing to use any RPCs, this tool can currently create a new wallet file or display some basic information about an existing wallet, such as whether the wallet is encrypted, whether it uses an HD seed, how many transactions it contains, and how many address book entries it has.
- Since version 2.16.0, Groestlcoin Core's built-in wallet has defaulted to generating P2SH-wrapped segwit addresses when users want to receive payments. These addresses are backwards compatible with all widely used software. Starting with Groestlcoin Core 2.20.1 (expected about a year after 2.18.2), Groestlcoin Core will default to native segwitaddresses (bech32) that provide additional fee savings and other benefits. Currently, many wallets and services already support sending to bech32 addresses, and if the Groestlcoin Core project sees enough additional adoption, it will instead default to bech32 receiving addresses in Groestlcoin Core 2.19.1. P2SH-wrapped segwit addresses will continue to be provided if the user requests them in the GUI or by RPC, and anyone who doesn't want the update will be able to configure their default address type. (Similarly, pioneering users who want to change their default now may set the addresstype=bech32 configuration option in any Groestlcoin Core release from 2.16.0 up.)
- BIP 61 reject messages are now deprecated. Reject messages have no use case on the P2P network and are only logged for debugging by most network nodes. Furthermore, they increase bandwidth and can be harmful for privacy and security. It has been possible to disable BIP 61 messages since v2.17.2 with the -enablebip61=0 option. BIP 61 messages will be disabled by default in a future version, before being removed entirely.
- The submitblock RPC previously returned the reason a rejected block was invalid the first time it processed that block but returned a generic "duplicate" rejection message on subsequent occasions it processed the same block. It now always returns the fundamental reason for rejecting an invalid block and only returns "duplicate" for valid blocks it has already accepted.
- A new submitheader RPC allows submitting block headers independently from their block. This is likely only useful for testing.
- The signrawtransactionwithkey and signrawtransactionwithwallet RPCs have been modified so that they also optionally accept a witnessScript, the witness script in the case of a P2WSH orP2SH-P2WSH output. This is compatible with the change to listunspent.
- For the walletprocesspsbt and walletcreatefundedpsbt RPCs, if thebip32derivs parameter is set to true but the key metadata for a public key has not been updated yet, then that key will have a derivation path as if it were just an independent key (i.e. no derivation path and its master fingerprint is itself).
- The -usehd configuration option was removed in version 2.16.0 From that version onwards, all new wallets created are hierarchical deterministic wallets. This release makes specifying -usehd an invalid configuration option.
- This release allows peers that your node automatically disconnected for misbehaviour (e.g. sending invalid data) to reconnect to your node if you have unused incoming connection slots. If your slots fill up, a misbehaving node will be disconnected to make room for nodes without a history of problems (unless the misbehaving node helps your node in some other way, such as by connecting to a part of the Internet from which you don't have many other peers). Previously, Groestlcoin Core banned the IP addresses of misbehaving peers for a period (default of 1 day); this was easily circumvented by attackers with multiple IP addresses. If you manually ban a peer, such as by using the setban RPC, all connections from that peer will still be rejected.
- The key metadata will need to be upgraded the first time that the HDseed is available. For unencrypted wallets this will occur on wallet loading. For encrypted wallets this will occur the first time the wallet is unlocked.
- Newly encrypted wallets will no longer require restarting the software. Instead such wallets will be completely unloaded and reloaded to achieve the same effect.
- A sub-project of Bitcoin Core now provides Hardware Wallet Interaction (HWI) scripts that allow command-line users to use several popular hardware key management devices with Groestlcoin Core. See their project page for details.
- This release changes the Random Number Generator (RNG) used from OpenSSL to Groestlcoin Core's own implementation, although entropy gathered by Groestlcoin Core is fed out to OpenSSL and then read back in when the program needs strong randomness. This moves Groestlcoin Core a little closer to no longer needing to depend on OpenSSL, a dependency that has caused security issues in the past. The new implementation gathers entropy from multiple sources, including from hardware supporting the rdseed CPU instruction.
- On macOS, Groestlcoin Core now opts out of application CPU throttling ("app nap") during initial blockchain download, when catching up from over 100 blocks behind the current chain tip, or when reindexing chain data. This helps prevent these operations from taking an excessively long time because the operating system is attempting to conserve power.
How to Upgrade?
If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), then run the installer.
If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), run the dmg and drag Groestlcoin Core to Applications.
Other Linux http://groestlcoin.org/forum/index.php?topic=97.0
Download Download the Windows Installer (64 bit) here Download the Windows Installer (32 bit) here Download the Windows binaries (64 bit) here Download the Windows binaries (32 bit) here Download the OSX Installer here Download the OSX binaries here Download the Linux binaries (64 bit) here Download the Linux binaries (32 bit) here Download the ARM Linux binaries (64 bit) here Download the ARM Linux binaries (32 bit) here
ALL NEW - Groestlcoin Moonshine iOS/Android Wallet
Built with React Native, Moonshine utilizes Electrum-GRS's JSON-RPC methods to interact with the Groestlcoin network.
GRS Moonshine's intended use is as a hot wallet. Meaning, your keys are only as safe as the device you install this wallet on. As with any hot wallet, please ensure that you keep only a small, responsible amount of Groestlcoin on it at any given time.
- Groestlcoin Mainnet & Testnet supported
- Bech32 support
- Multiple wallet support
- Electrum - Support for both random and custom peers
- Encrypted storage
- Biometric + Pin authentication
- Custom fee selection
- Import mnemonic phrases via manual entry or scanning
- RBF functionality
- BIP39 Passphrase functionality
- Support for Segwit-compatible & legacy addresses in settings
- Support individual private key sweeping
- UTXO blacklisting - Accessible via the Transaction Detail view, this allows users to blacklist any utxo that they do not wish to include in their list of available utxo's when sending transactions. Blacklisting a utxo excludes its amount from the wallet's total balance.
- Ability to Sign & Verify Messages
- Support BitID for password-free authentication
- Coin Control - This can be accessed from the Send Transaction view and basically allows users to select from a list of available UTXO's to include in their transaction.
- Ability to Broadcast raw transactions
Download iOS Android
ALL NEW! – HODL GRS Android Wallet
HODL GRS connects directly to the Groestlcoin network using SPV mode and doesn't rely on servers that can be hacked or disabled.
HODL GRS utilizes AES hardware encryption, app sandboxing, and the latest security features to protect users from malware, browser security holes, and even physical theft. Private keys are stored only in the secure enclave of the user's phone, inaccessible to anyone other than the user.
Simplicity and ease-of-use is the core design principle of HODL GRS. A simple recovery phrase (which we call a Backup Recovery Key) is all that is needed to restore the user's wallet if they ever lose or replace their device. HODL GRS is deterministic, which means the user's balance and transaction history can be recovered just from the backup recovery key.
- Simplified payment verification for fast mobile performance
- No server to get hacked or go down
- Single backup phrase that works forever
- Private keys never leave your device
- Import password protected paper wallets
- Payment protocol payee identity certification
Download Main Release (Main Net) Testnet Release
ALL NEW! – GroestlcoinSeed Savior
Groestlcoin Seed Savior is a tool for recovering BIP39 seed phrases.
This tool is meant to help users with recovering a slightly incorrect Groestlcoin mnemonic phrase (AKA backup or seed). You can enter an existing BIP39 mnemonic and get derived addresses in various formats.
To find out if one of the suggested addresses is the right one, you can click on the suggested address to check the address' transaction history on a block explorer.
- If a word is wrong, the tool will try to suggest the closest option.
- If a word is missing or unknown, please type "?" instead and the tool will find all relevant options.
Live Version (Not Recommended) https://www.groestlcoin.org/recovery/
ALL NEW! – Vanity Search Vanity Address Generator NOTE: NVidia GPU or any CPU only. AMD graphics cards will not work with this address generator.
VanitySearch is a command-line Segwit-capable vanity Groestlcoin address generator. Add unique flair when you tell people to send Groestlcoin. Alternatively, VanitySearch can be used to generate random addresses offline.
If you're tired of the random, cryptic addresses generated by regular groestlcoin clients, then VanitySearch is the right choice for you to create a more personalized address.
VanitySearch is a groestlcoin address prefix finder. If you want to generate safe private keys, use the -s option to enter your passphrase which will be used for generating a base key as for BIP38 standard (VanitySearch.exe -s "My PassPhrase" FXPref). You can also use VanitySearch.exe -ps "My PassPhrase" which will add a crypto secure seed to your passphrase.
VanitySearch may not compute a good grid size for your GPU, so try different values using -g option in order to get the best performances. If you want to use GPUs and CPUs together, you may have best performances by keeping one CPU core for handling GPU(s)/CPU exchanges (use -t option to set the number of CPU threads).
- Fixed size arithmetic
- Fast Modular Inversion (Delayed Right Shift 62 bits)
- SecpK1 Fast modular multiplication (2 steps folding 512bits to 256bits using 64 bits digits)
- Use some properties of elliptic curve to generate more keys
- SSE Secure Hash Algorithm SHA256 and RIPEMD160 (CPU)
- Multi-GPU support
- CUDA optimisation via inline PTX assembly
- Seed protected by pbkdf2_hmac_sha512 (BIP38)
- Support P2PKH, P2SH and BECH32 addresses
- Support split-key vanity address
ALL NEW! – Groestlcoin EasyVanity 2020
Groestlcoin EasyVanity 2020 is a windows app built from the ground-up and makes it easier than ever before to create your very own bespoke bech32 address(es) when whilst not connected to the internet.
If you're tired of the random, cryptic bech32 addresses generated by regular Groestlcoin clients, then Groestlcoin EasyVanity2020 is the right choice for you to create a more personalised bech32 address. This 2020 version uses the new VanitySearch to generate not only legacy addresses (F prefix) but also Bech32 addresses (grs1 prefix).
- Ability to continue finding keys after first one is found
- Includes warning on start-up if connected to the internet
- Ability to output keys to a text file (And shows button to open that directory)
- Show and hide the private key with a simple toggle switch
- Show full output of commands
- Ability to choose between Processor (CPU) and Graphics Card (GPU) ( NVidia ONLY! )
- Features both a Light and Dark Material Design-Style Themes
- Free software - MIT. Anyone can audit the code.
- Written in C# - The code is short, and easy to review.
Remastered! – Groestlcoin WPF Desktop Wallet (v188.8.131.52)
Groestlcoin WPF is an alternative full node client with optional lightweight 'thin-client' mode based on WPF. Windows Presentation Foundation (WPF) is one of Microsoft's latest approaches to a GUI framework, used with the .NET framework. Its main advantages over the original Groestlcoin client include support for exporting blockchain.dat and including a lite wallet mode.
This wallet was previously deprecated but has been brought back to life with modern standards.
- Works via TOR or SOCKS5 proxy
- Can use bootstrap.dat format as blockchain database
- Import/Export blockchain to/from bootstrap.dat
- Import wallet.dat from Groestlcoin-qt wallet
- Export wallet to wallet.dat
- Use both groestlcoin-wpf and groestlcoin-qt with the same addresses in parallel. When you send money from one program, the transaction will automatically be visible on the other wallet.
- Rescan blockchain with a simple mouse click
- Works as a full node and listens to port 1331 (listening port can be changed)
- Fast Block verifying, parallel processing on multi-core CPUs
- Mine Groestlcoins with your CPU by a simple mouse click
- All private keys are kept encrypted on your local machine (or on a USB stick)
- Lite - Has a lightweight "thin client" mode which does not require a new user to download the entire Groestlcoin chain and store it
- Free and decentralised - Open Source under GNU license
- Bech32 support
- P2sh support
- Fixed Import/Export to wallet.dat
- Testnet Support
- Rescan wallet option
- Change wallet password option
- Address type and Change type options through *.conf file
- Import from bootstrap.dat - It is a flat, binary file containing Groestlcoin blockchain data, from the genesis block through a recent height. All versions automatically validate and import the file "grs.bootstrap.dat" in the GRS directory. Grs.bootstrap.dat is compatible with Qt wallet. GroestlCoin-Qt can load from it.
- In Full mode file %APPDATA%\Groestlcoin-WPF\GRS\GRS.bootstrap.dat is full blockchain in standard bootstrap.dat format and can be used with other clients.
ALL NEW! – BIP39 Key Tool
Groestlcoin BIP39 Key Tool is a GUI interface for generating Groestlcoin public and private keys. It is a standalone tool which can be used offline.
- Selection options for 3-24 words (simply putting the space separated words in the first word box will also work) along with a bip39 passphrase
- User input for total number of addresses desired
- Creation of P2PKH, P2SH, P2WPKH and P2WSH addresses along with xpriv and xpub as per BIP32 spec, using a word list as the starting point following the BIP39 standard.
- Pre-sets for BIP44, BIP49, BIP84 and BIP141 standards, along with custom user input for derivation path
- Option for Hardened or non-hardened addresses
- Option for Testnet private and public keys
- Output containing derivation path, private key in WIF, integer and hex format, public key address, public point on curve and scriptpubkey
- Results are output in a file titled 'wallet.txt' with the time addresses were generated, along with all information presented onscreen
Download Windows Linux
pip3 install -r requirements.txt python3 bip39\_gui.py
ALL NEW! – Electrum Personal Server
Groestlcoin Electrum Personal Server aims to make using Electrum Groestlcoin wallet more secure and more private. It makes it easy to connect your Electrum-GRS wallet to your own full node.
It is an implementation of the Electrum-grs server protocol which fulfils the specific need of using the Electrum-grs wallet backed by a full node, but without the heavyweight server backend, for a single user. It allows the user to benefit from all Groestlcoin Core's resource-saving features like pruning, blocks only and disabled txindex. All Electrum-GRS's feature-richness like hardware wallet integration, multi-signature wallets, offline signing, seed recovery phrases, coin control and so on can still be used, but connected only to the user's own full node.
Full node wallets are important in Groestlcoin because they are a big part of what makes the system be trust-less. No longer do people have to trust a financial institution like a bank or PayPal, they can run software on their own computers. If Groestlcoin is digital gold, then a full node wallet is your own personal goldsmith who checks for you that received payments are genuine.
Full node wallets are also important for privacy. Using Electrum-GRS under default configuration requires it to send (hashes of) all your Groestlcoin addresses to some server. That server can then easily spy on your transactions. Full node wallets like Groestlcoin Electrum Personal Server would download the entire blockchain and scan it for the user's own addresses, and therefore don't reveal to anyone else which Groestlcoin addresses they are interested in.
Groestlcoin Electrum Personal Server can also broadcast transactions through Tor which improves privacy by resisting traffic analysis for broadcasted transactions which can link the IP address of the user to the transaction. If enabled this would happen transparently whenever the user simply clicks "Send" on a transaction in Electrum-grs wallet.
Note: Currently Groestlcoin Electrum Personal Server can only accept one connection at a time.
- Use your own node
- Tor support
- Uses less CPU and RAM than ElectrumX
- Used intermittently rather than needing to be always-on
- Doesn't require an index of every Groestlcoin address ever used like on ElectrumX
Download Windows Linux / OSX
UPDATED – Android Wallet 7.38.1 - Main Net + Test Net
The app allows you to send and receive Groestlcoin on your device using QR codes and URI links.
When using this app, please back up your wallet and email them to yourself! This will save your wallet in a password protected file. Then your coins can be retrieved even if you lose your phone.
- Add confidence messages, helping users to understand the confidence state of their payments.
- Handle edge case when restoring via an external app.
- Count devices with a memory class of 128 MB as low ram.
- Introduce dark mode on Android 10 devices.
- Reduce memory usage of PIN-protected wallets.
- Tapping on the app's version will reveal a checksum of the APK that was installed.
- Fix issue with confirmation of transactions that empty your wallet.
Download Main Net Main Net (FDroid) Test Net
UPDATED – Groestlcoin Sentinel 3.5.06 (Android)
Groestlcoin Sentinel is a great solution for anyone who wants the convenience and utility of a hot wallet for receiving payments directly into their cold storage (or hardware wallets).
Sentinel accepts XPUB's, YPUB'S, ZPUB's and individual Groestlcoin address. Once added you will be able to view balances, view transactions, and (in the case of XPUB's, YPUB's and ZPUB's) deterministically generate addresses for that wallet.
Groestlcoin Sentinel is a fork of Groestlcoin Samourai Wallet with all spending and transaction building code removed.
- Removed Cryptopia
- Added adaptive icons for Android 8 and above
- Add block book block explorer
UPDATED – P2Pool Test Net
- Add compatibility for Groestlcoin Core 2.18.2
Pre-Hosted Testnet P2Pool is available via http://testp2pool.groestlcoin.org:21330/static/
IRC Log from Ravencoin Open Developer Meeting - Aug 10, 2018
submitted by __pathfinder__ to Ravencoin [link] [comments]
[16:01] <@Wolfsokta> Todays topics: DGW implementation, segfault, Q&A, feedback on IRC
[16:01] <@Wolfsokta> Just to set the stage here, this is a developer meeting where developers that have contributed source code to the Ravencoin project can meet and chat about items they are working on. Please be respectful to one another. For the sake of staying on target, please limit interactions to questions and comments on code or projects that you are working on. Any time left over at the end can be opened up for general Q&A.
[16:02] <@Wolfsokta> FYI - I'm RavencoinDev, and lets get started.
[16:03] <@Wolfsokta> @Tron, can you talk about where we are at with DGW on testnet and mainnet?
[16:03] <@Tron> Sure.
[16:03] can someone volunteer to take notes and post also?
[16:03] <@Tron> We are building binaries that will activate DGW-180 at block 338778
[16:04] <@Tron> It looks back 180 blocks to calculate the diff.
[16:04] I will copy the text from the meeting into a file that can be archived later. I can also make summary notes after like BTC core does.
[16:04] I'll save a log of the whole meeting and can post it on the subreddit thread.
[16:04] <@Wolfsokta> We have setup testnet4 in order to test the new binaries.
[16:05] <@Wolfsokta> We plan to release the binaries later today.
[16:05] @Tron have you looked into the timestamp attack concerns of DGW?
[16:06] <@Tron> Yes. And for that reason, we've tightened up the timestamps that will be accepted for valid blocks.
[16:06] <@Tron> Moved from 2h to 12 minutes.
[16:06] Oh wow okay
[16:06] <@Tron> Its also the reason we went from 60 blocks (lookback) to 180 blocks.
[16:07] why would 2h ever be acceptable? lol
[16:07] 2h was originally used for daylight savings shenanigans I believe
[16:07] <@Tron> It was from bitcoin, and it factors in clock skew, and variance in finding blocks on 10 minute intervals, and block propagation time.
[16:07] makes sense
[16:08] what about the segmentation fault when reindexing?
[16:08] any fix yet?
[16:08] @Tron 12 minutes seems to be pretty small window for clock skew
[16:08] I assume it was chosen due to 1/10th scaling from BTC?
[16:09] <@Wolfsokta> Not yet ruski, we'll cover that in a bit.
[16:09] <@Tron> We did divide existing by 10.
[16:10] <@Wolfsokta> Any further questions about DGW on testnet or on mainnet?
[16:10] What block is it activating on mainnet?
[16:10] <@Wolfsokta> 338778
[16:11] And will there be the need to update binaries twice (for DGW fork and asset layer fork)?
[16:11] <@Tron> We are activating DGW by block height because headers sync first, and the BIP9 activation flag sets a flag, and we need to look at either block height or version to know which diff algo.
[16:11] <@Wolfsokta> Calculated to be near the end of the month so we have some time with DGW on testnet.
[16:11] Someone on discord asked this a while back, but why Was DGW chosen over something like digishield or anyother algo
[16:11] <@Tron> And block version can be changed (tampering) and still make it on the chain.
[16:12] Binaries will need to be updated as more asset layer stuff get completed and tested. Not by the end of the month though.
[16:12] <@Tron> We looked at DGW and LWMA. LWMA has a lot of constants that must be tuned right.
[16:13] <@Tron> We were impressed with the amount of work on LWMA to analyze how it responds, but it wasn't straightforward to understand the nuances of how/why it works.
[16:13] zawy was in the #development channel on Discord. He's an expert on DAAs. I'm sure he would help with tuning LWMA if you asked.
[16:14] <@Tron> Either will be much better that what we have. Even at the extremes, it will adjust smoothly.
[16:14] Are there any issues or comments on the DGW code that should be addressed?
[16:14] @devs in general
[16:15] <@Wolfsokta> Thanks @brianmct, we did look extensively at the DGW code to ensure we weren't going to see the same issues that happened to Verge.
[16:16] so i guess you would have to make way more blocks with false timestamps to be able to exploit our version of dgw right?
[16:16] because of the 12 minute timestamp thing?
[16:16] <@Wolfsokta> With X16R, and with the changes Tron talked about we feel confident that this will address the swings without being able to be exploited.
[16:17] @russki Yeah, pretty much.
[16:17] verge is a different type of situation - but overall asics and mining are a risk always
[16:18] <@Wolfsokta> Okay, anything else on the difficulty targeting change?
[16:19] <@Wolfsokta> Cool, blondfrogs wanted to talk about subassets that were added.
[16:19] ooh yeah i saw those github commits
[16:19] looking good
[16:19] We also want to let everyone know that you can now create sub assets with the new binaries that will be posted soon. You can create these subassets using the issue rpc call. Qt will be built shortly. This will allow users to make an asset PARENT
[16:20] <@Wolfsokta> Basic overview. If you own an asset you can create sub-assets by including a '/
[16:20] And then make any of the following PARENT/A PARENT/B .... PARENT/Z
[16:20] <@Tron> We'll post a FAQ on assets later today.
[16:21] <@Wolfsokta> And it only is 100 Raven for a subasset
[16:21] on testnetv4 it still says asset activation status: waiting
[16:21] <@Tron> Yep, it needs to be voted in.
[16:21] <@Wolfsokta> We wanted to test the BIP9 activation process again as well. The more testing the better.
[16:21] We wanted to make sure that we follow the same process the Mainnet is going to go through.
[16:21] ok nice
[16:22] <@Wolfsokta> Any questions about subassets?
[16:23] are they unique?
[16:23] <@Tron> No
[16:23] <@Wolfsokta> Yes, they behave the same way as a normal asset, just live under an owned asset.
[16:23] <@Tron> Maybe I misunderstood the question. Unique with parent.
[16:23] Each subasset can have their own number issued? So PARENT/A can have 1,000 and PARENT/B can be 50?
[16:23] oooh ok that makes more sense
[16:23] <@Wolfsokta> Exactly thanks traysi
[16:24] <@Tron> And, not the same thing as "Unique Assets"
[16:24] <@Wolfsokta> The individual unique asset support is included in an upcoming phase.
[16:25] Moving onto the Segfault issue ----------------------->>>>>>>>>>> SEGFAULT
[16:25] Are we able to changes the properties of subassets after they have been created? Or is something like that specified when creating them?
[16:25] <@Tron> Yes
[16:25] can sub-assets be reassigned to other addresses while retaining control of the parent asset elsewhere?
[16:25] So basically it has all the features of a normal asset, but live under an asset's top-level namespace?
[16:25] satoshi corbie @russkidooski
[16:25] So basically it has all the features of a normal asset, but live under an asset's top-level namespace?
[16:26] <@Tron> Sub-assets are identical to assets after creation.
[16:26] <@Tron> Just cheaper to create, and in your "owned" namespace.
[16:26] Okay cool
[16:26] will subassets eventually have a unqiue tag? eg ASSET/SUB:1
[16:26] We have found an issue with our testnet binaries and are still looking to the issue. The issue presents itself when a user performs a reindexing of the chain. We think we have pinpointed the where the problem is and are currently working a fix. This fix will be out shortly.
[16:26] plan is to make default reissue=true and units=0 and allow increase in units on reissue
[16:26] How much is it going to be for a sub-asset?
[16:27] <@Wolfsokta> Okay, let's now focus on the SegFault issue that was discovered by Under.
[16:28] do you know what the issue was?
[16:28] <@Wolfsokta> It seems to be a build problem with the boost library.
[16:28] Still looking into though. :)
[16:29] <@Wolfsokta> We have been able to reproduce it on linux internally with 2.0.3
[16:29] yea i get the same issue on windows 10
[16:30] I saw a Bitcoin thread a while back about the seg fault error. I had it because I had conflicting versions of BDB
[16:30] static compiled on ubuntu 18.04
[16:30] <@Wolfsokta> We really appreciate you guys pulling down master and helping test.
[16:30] @Trap we will look into that also
[16:30] no problem, im just curious lol
[16:32] <@Wolfsokta> We haven't been able to build a windows version that doesn't have the segfault issue.
[16:32] <@Tron> We're dropping Windows support ;)
[16:33] Just finished setting up a new Windows test environment so we can test and validate the solution as we are working on it.
[16:33] The bdb issue is a known issue that has been around for some time. We are pretty certain it is a boost library issue, and are working quickly to get a windows build that fixes the issue.
[16:34] what did you guys do to fix the linux version?
[16:34] Once we have binaries for all supported platforms ready, hopefully tonight. No promises. We will make an announcement
[16:34] The issue has been fixed on Linux and Mac though?
[16:34] (oops sorry already answered)
[16:34] <@Wolfsokta> If anybody else gets there first with Windows please let us know what you found.
[16:34] Built the binairies on a Ubuntu 16.04 box.
[16:34] that was it?
[16:35] Yeah, we think so. 16.04 has boost 1.58 which seems to fix the issue. The build on 18.04 use boost 1.67 which seems to cause the issue.
[16:35] is there a boost 1.58 repo on 18.04?
[16:35] 18.04 used 1.65***
[16:36] I've built with boost 1.68 on arch Linux
[16:36] It worked
[16:37] wallet 2.0.x?
[16:37] @Trap, the issue is when -reindex is used.
[16:37] Oh sorry my bad
[16:37] Wallet 2.0.3
[16:38] <@Wolfsokta> For those that joined late we're discussing https://github.com/RavenProject/Ravencoin/issues/208
[16:38] 1 sec im going to boot into ubuntu and try compiling with 1.58 on 18.04
[16:39] Any other questions pertaining to the segfault?
[16:40] <@Wolfsokta> Alright, thanks everybody. Before we start the Q&A I would like to get some quick feedback on using IRC for this meeting.
[16:41] If we're going to use IRC we should take some measures to at least hide people's IPs when they join
[16:42] Yea. It is very hard to read this back.
[16:42] Also no message history
[16:42] If you disconnect and reconnect
[16:42] <@Tron> I'll throw in a vote for Discord.
[16:43] <@Wolfsokta> If you use a decent IRC client instead of the website it's not bad.
[16:43] Some of us used a VPN before we connected to IRC
[16:43] If needed we can restrict channel to Developer roles, etc for the developer meeting and open it up for general Q&A
[16:43] Make a discord when only mods can submit links
[16:45] Discord won the poll 5 to 2
[16:45] <@Wolfsokta> There are also a lot of IRC tools that can be used to track the meetings.
[16:45] we know
[16:46] <@Wolfsokta> We also want any developer to be able to speak.
[16:48] <@Wolfsokta> We're open to try Discord next week.
[16:48] <[kai]> perhaps you could even get a feed from this irc to discord?
[16:49] <[kai]> a feed would enable discordians to view the chat, but only contribute if they take the extra steps to come here.
[16:49] <@Wolfsokta> That's a good idea kai... Has anybody seen that working?
[16:50] <[kai]> https://github.com/reactiflux/discord-irc
[16:50] <[kai]> im sure you could make this a one way deal.
[16:51] <@Wolfsokta> I like that idea, let's try that for next week. So we'll meet here in IRC again, but it should be broadcast to Discord.
[16:53] <@Wolfsokta> Okay, we'll go with IRC next week with the broadcast to discord and re-visit for next week.
[16:54] <@Wolfsokta> Okay, let's do open Q&A for the next few mins.
[16:54] <[kai]> just a quickey, more for my curioisty, did you look at digishield?
[16:54] <[kai]> DGW solution seems solid.
[16:55] <[kai]> was just curious if it was one of the four solutions you looked at.
[16:55] <@Wolfsokta> Tron is answering... Any others Q?
[16:55] <@Tron> We briefly looked at Digishield, but our analysis was between DGW and LWMA.
[16:55] <[kai]> right on.
[16:56] <[kai]> cheers guys, see you next time.
[16:56] OPen the gates for the last 4 minutes for any other questions?
[16:58] <@Wolfsokta> Alright, thank you all for being here today and please join the development effort with us. If you have an idea, or a fix for an issue write it up and submit a pull request.
[16:59] <@Wolfsokta> Thanks again for all those that have contributed their time and effort to make Ravencoin successful. We have the BEST community.
6:59] You devs are pretty cool
[16:59] did the burn get discussed?
[16:59] <@Wolfsokta> Special thanks to Bruce, really glad you could make it with the short notice.
[17:00] <@Tron> Thanks everyone!
Armory Wallet Has Failed Me! Can I recover BTC?
So I opted to migrate from coinbase to a local wallet. submitted by andhof-mt to Bitcoin [link] [comments]
Naturally, I download Armory and shoot it a send for 1BTC. 225 confirmations on the SEND, but wallet never receives it.
Turns out, running Armory wallet has been corrupting my database. Every time I run it a background process it spawns causes Bitcoin-QT to fail.
I've tried uninstalling and re-installing bitcoin, armory wallet three times. I've deleted my bitcoin directory in %appdata%, ensured downloads are never interrupted.
Is there any way at all for me to recover the BitCoin I sent to armory wallet provided I can never get armory wallet to work correctly?
Any help appreciated. Here is the errors:
2015-08-21 14:48:15 init message: Activating best chain... 2015-08-21 14:49:23 Corruption: block checksum mismatch 2015-08-21 14:49:23 *** System error while flushing: Database corrupted
I keep reading people say bitcoin development is stalled
submitted by BillyHodson to Bitcoin [link] [comments]
But in practice there's more going on right now than there's ever been in the last few years. You just have to look in the right places. Here's a few days of documented github activity from the bitcoin slack and I've a feeling there are hundreds more people working on Bitcoin projects outside of the work being done by core:
github BOT [6:28 PM] [bitcoin:master] 2 new commits by Daniel Kraft and 1 other: f93c2a1 net: Avoid duplicate getheaders requests. - Daniel Kraft 8e8bebc Merge #8054: net: Avoid duplicate getheaders requests. - Wladimir J. van der Laan
[6:28] [bitcoin/bitcoin] Pull request closed: #8054 net: Avoid duplicate getheaders requests. by laanwj
[6:31] [bitcoin:master] 6 new commits by Pieter Wuille and 1 other: d253ec4 Make ProcessNewBlock dbp const and update comment - Pieter Wuille 316623f Switch reindexing to AcceptBlock in-loop and ActivateBestChain afterwards - Pieter Wuille fb8fad1 Optimize ActivateBestChain for long chains - Pieter Wuille d3d7547 Add -reindex-chainstate that does not rebuild block index - Pieter Wuille b4d24e1 Report reindexing progress in GUI - Pieter Wuille Show more...
[6:31] [bitcoin/bitcoin] Pull request closed: #7917 Optimize reindex by laanwj
Joshua Unseth [9:55 PM] joined #commit-activity. Also, @sjors joined and left.
----- May 19th -----
github BOT [12:08 AM] [bitcoin/bitcoin] Pull request submitted by EthanHeilman
8070 Remove non-determinism which is breaking net_tests #8069
If addrmanUncorrupted does not have the same nKey every time it will map addrs to different bucket positions and occasionally cause a collision between two addrs, breaking the test.
github BOT [1:00 AM] [bitcoin/bitcoin] Pull request closed: #7716 [0.11] Backport BIP9 and softfork for BIP's 68,112,113 by morcos
Eragmus You Should Probably Stop Modding [1:12 AM] joined #commit-activity. Also, @buttmunch joined, @icandothisallday joined, @misnomer joined, @coreneedstostop joined, @xchins joined, @jbeener joined, @jbleeks joined, @whalepanda joined, @grinny joined, @alex_may joined, @mr_e joined.
github BOT [2:46 PM] [bitcoin:master] 5 new commits by Warren Togami and 1 other: 00678bd Make failures to connect via Socks5() more informative and less unnecessarily scary. - Warren Togami 0d9af79 SOCKS5 connecting and connected messages with -debug=net. - Warren Togami 94fd1d8 Make Socks5() InterruptibleRecv() timeout/failures informative. - Warren Togami bf9266e Use Socks5ErrorString() to decode error responses from socks proxy. - Warren Togami 18436d8 Merge #8033: Fix Socks5() connect failures to be less noisy and less unnecessarily scary - Wladimir J. Show more...
[2:46] [bitcoin/bitcoin] Pull request closed: #8033 Fix Socks5() connect failures to be less noisy and less unnecessarily scary by laanwj
github BOT [3:56 PM] [bitcoin:master] 3 new commits by EthanHeilman and 2 others: f4119c6 Remove non-determinism which is breaking net_tests #8069 - EthanHeilman 2a8b358 Fix typo adddrman to addrman as requested in #8070 - Ethan Heilman 7771aa5 Merge #8070: Remove non-determinism which is breaking net_tests #8069 - Wladimir J. van der Laan
[3:56] [bitcoin/bitcoin] Pull request closed: #8070 Remove non-determinism which is breaking net_tests #8069 by laanwj
github BOT [5:18 PM] [bitcoin/bitcoin] Pull request submitted by MarcoFalke
8072 travis: 'make check' in parallel and verbose
• 'make check' in parallel, since the log will take care of clean output • 'make check' verbose, so that test failure causes aren't hidden
github BOT [7:56 PM] [bitcoin/bitcoin] Pull request submitted by rat4
8073 qt: askpassphrasedialog: Clear pass fields on accept
This is usability improvement in a case if user gets re-asked passphrase. (e.g. made a typo)
Victor Broman [8:01 PM] joined #commit-activity. Also, @bb joined, @ziiip joined.
----- May 20th -----
github BOT [12:34 PM] [bitcoin/bitcoin] Pull request submitted by jsantos4you
[12:37] [bitcoin/bitcoin] Pull request closed: #8075 0.12 by sipa
github BOT [3:37 PM] [bitcoin/bitcoin] Pull request closed: #7082 Do not absolutely protect local peers and make eviction more aggressive. by gmaxwell
github BOT [3:44 PM] [bitcoin:master] 2 new commits by Cory Fields and 1 other: 401ae65 travis: 'make check' in parallel and verbose - Cory Fields 1b87e5b Merge #8072: travis: 'make check' in parallel and verbose - MarcoFalke
[3:44] [bitcoin/bitcoin] Pull request closed: #8072 travis: 'make check' in parallel and verbose by MarcoFalke
github BOT [3:58 PM] [bitcoin/bitcoin] Pull request closed: #7093 Address mempool information leak and resource wasting attacks. by gmaxwell
github BOT [6:11 PM] [bitcoin/bitcoin] Pull request submitted by sdaftuar
8076 VerifyDB: don't check blocks that have been pruned
If a pruning node ends up in a state where it has very few blocks on disk, then a node could fail to start up in VerifyDB. This pull changes the behavior for pruning nodes, so that we will just not bother trying to check blocks that have been pruned.
I don't expect this edge case to be triggered much in practice currently; this is a preparatory commit for segwit (to deal with the case of pruning nodes that upgrade after segwit activation).
Erik Hedman [6:20 PM] joined #commit-activity
github BOT [8:46 PM] [bitcoin/bitcoin] Pull request submitted by jtimon
8077 Consensus: Decouple from chainparams.o and timedata.o
Do it for the consensus-critical functions:
• CheckBlockHeader • CheckBlock • ContextualCheckBlockHeader Show more...
github BOT [9:26 PM] [bitcoin:master] 3 new commits by MarcoFalke: fac9349 [qa] Remove hardcoded "4 nodes" from test_framework - MarcoFalke fad68f7 [qa] Reduce node count for some tests - MarcoFalke 8844ef1 Merge #8056: [qa] Remove hardcoded "4 nodes" from test_framework - MarcoFalke
[9:27] [bitcoin/bitcoin] Pull request closed: #8056 [qa] Remove hardcoded "4 nodes" from test_framework by MarcoFalke
github BOT [9:48 PM] [bitcoin/bitcoin] Pull request submitted by petertodd
8078 Disable the mempool P2P command when bloom filters disabled
Only useful to SPV peers, and attackers... like bloom is a DoS vector as far more data is sent than received.
null radix [10:15 PM] joined #commit-activity
github BOT [11:34 PM] [bitcoin:master] 2 new commits by MarcoFalke: fab5233 [qa] test_framework: Set wait-timeout for bitcoind procs - MarcoFalke 37f9a1f Merge #8047: [qa] test_framework: Set wait-timeout for bitcoind procs - MarcoFalke
[11:34] [bitcoin/bitcoin] Pull request closed: #8047 [qa] test_framework: Set wait-timeout for bitcoind procs by MarcoFalke
github BOT [11:48 PM] [bitcoin/bitcoin] Pull request closed: #7826 [Qt] show conflicts of unconfirmed transactions in the UI by jonasschnelli
[11:50] [bitcoin/bitcoin] Pull request re-opened: #7826 [Qt] show conflicts of unconfirmed transactions in the UI by jonasschnelli
----- May 21st ----- Rentaro Matsukata [1:56 AM] joined #commit-activity. Also, @evilone joined, @cryptop joined, @thomas5 joined.
github BOT [1:54 PM] [bitcoin/bitcoin] Pull request submitted by gmaxwell
8080 Do not use mempool for GETDATA for tx accepted after the last mempool req.
The ability to GETDATA a transaction which has not (yet) been relayed is a privacy loss vector.
The use of the mempool for this was added as part of the mempool p2p message and is only needed to fetch transactions returned by it.
github BOT [5:48 PM] [bitcoin/bitcoin] Pull request submitted by gmaxwell
8082 Defer inserting into maprelay until just before relaying.
Also extend the relaypool lifetime by 1 minute (6%) to 16 minutes.
This reduces the rate of not founds by better matching the far end expectations, it also improves privacy by removing the ability to use getdata to probe for a node having a txn before Show more...
Sergey Ukustov [9:17 PM] joined #commit-activity. Also, @stoicism joined.
----- Yesterday May 22nd, 2016 -----
github BOT [5:59 AM] [bitcoin/bitcoin] Pull request submitted by jonasschnelli
8083 Add support for dnsseeds with option to filter by servicebits
Opposite part of https://github.com/sipa/bitcoin-seedepull/36
. Including new testnet seed that supports filtering.
Required for SW #7910.
Junseth Sock Puppet Account [6:13 AM] joined #commit-activity
github BOT [1:59 PM] [bitcoin/bitcoin] Pull request submitted by gmaxwell
8084 Add recently accepted blocks and txn to AttemptToEvictConnection.
This protect any not-already-protected peers who were the most recent to relay transactions and blocks to us.
This also takes increases the eviction agressiveness by making it willing to disconnect a netgroup with only one member.
github BOT [5:04 PM] [bitcoin/bitcoin] Pull request submitted by theuni
8085 p2p: Begin encapsulation
This work creates CConnman. The idea is to begin moving data structures and functionality out of globals in net.h and into an instanced class, in order to avoid side-effects in networking code. Eventually, an (internal) api begins to emerge, and as long as the conditions of that api are met, the inner-workings may be a black box.
For now (for ease), a single global CConnman is created. Down the road, the instance could be passed around instead. Also, CConnman should be moved out of net.h/net.cpp, Show more...
github BOT [5:14 PM] [bitcoin/bitcoin] Pull request submitted by sipa
8086 Use SipHash for node eviction
github BOT [5:50 PM] [bitcoin/bitcoin] Pull request closed: #6844 [REST] Add send raw transaction by lclc
----- Today May 23rd, 2016 ----- yannie888 [5:21 AM] joined #commit-activity. Also, @myco joined, @er_sham joined, @ethdealer joined.
github BOT [3:23 PM] [bitcoin/bitcoin] Pull request submitted by pstratem
8087 Introduce CBlockchain and move CheckBlockHeader
[3:23] [bitcoin/bitcoin] Pull request submitted by pstratem
8088 Avoid recalculating vchKeyedNetGroup in eviction logic.
Lazy calculate vchKeyedNetGroup in CNode::GetKeyedNetGroup.
Start Here for Much Wallet WOW!
submitted by Fulvio55 to dogecoin [link] [comments]
EDIT 2017-02-10: A word about Nodes
There is a discussion about nodes that came up today, where it seems I'm discouraging people from running the full QT/Core client. Yes and No. What I'm trying to make sure people understand is how things work, and that it is NOT mandatory to run a client in order to use Dogecoins (and yes, I realise that browser-based tools like coinb.in and wallet sweepers are 'clients' by strict definition)
That said, more nodes is absolutely a good thing for the network. Preferrably full nodes. How do you run a full node? Just run Core/QT and open up Port 22556 on your router so it can connect to more than 8 peers. What will it cost you? You need your machine to be on 24/7/365, you need enough storage for the full blockchain (currently about 20Gb. Bitcoin is over 120Gb)
and enough bandwidth to keep it in sync and share blocks with peers. A couple of Gb a month, most likely. This is best done with a desktop on a wired broadband link. Or maybe a hosted VM in the cloud. :)
EDIT 2017-01-09: Wallets WITHOUT Clients
Since I started helping people on /BitcoinBeginners
, I'm getting a lot of questions about how to use wallets without running clients or trusting third parties. So here are a couple of resources that will make that possible, and not just for Dogecoin: Multi-Coin Wallet Generator Now supporting 129 currencies! Coinb.in
Start by setting the currency, found in the gear wheel in the Broadcast tab. Dogecoin Wallet Sweeper
Redeem 'paper' wallets containing up to about 100 UTXOs. Bitinfo Charts
My favourite block explorer, handles a bunch of cryptos.
Using these resources, it is possible to hold, receive and spend coins in various currencies, without having to run QT or a 'lite' client. You can also download and run the pages on your own device.
EDIT 2016-11-23: SEMANTICS about MINING! :P
Even though there is already a section on mining below, it has been suggested given the huge number of posts on the subject that this needs to be made clearer. Since people get their panties in a twist over the word 'dead', lets change that...
MINING IS DEAD!
MINING DOGECOIN IS UNPROFITABLE!
Put simply, there is no way to mine Dogecoin and make a profit because of the massive hashpower provided by industrial-scale Litecoin miners. Mining Doge directly stopped being viable when our hashrate exploded with the introduction of AuxPoW. Mining with CPU's and GPU's died when ASICs were introduced. And mining with a laptop WILL kill your laptop and cost you a fortune to repair or replace. Mining Litecoin with an exchange that also mines Doge and others will earn less than the electricity consumed, and you won't recover your costs. Probably ever, but certainly not in any reasonable time.
Mining other currencies may be a thing, but that's beyond our scope here. This is /Dogecoin
, not /GetRichMiningCryptos
after all. If you want to mine the newest scamcoin for fun and profit, look elsewhere for advice. :/
Oh, and most important:
READ BEFORE YOU POST!
At any given time, there are half a dozen posts on the frontpage just like the one you're about to write
, where the answers have already been given. Read them. Don't make people waste their time repeating themselves because you were too lazy to bother reading stuff. :P So there I was, having a quiet Sundy arvo bludge, as you do, when 42points turned up on Facebook and asked me to write a new sticky post for /dogecoin. Why would he do this, when he should be having a bludge himself, I hear you ask? Well, seems he was doing exactly that, and wanted to fob off the work he’s too slack to do himself. ;) Ah well, being a sucker for punishment, I’ll grudgingly oblige I guess.
OK, first things first.
Dogecoin Core 1.10.0 2015-Nov-01
- A client is a piece of software you keep on your computer which holds one or more wallets. Here are the current client versions. If you're using an older client please upgrade to the newest version prior to sending/receiving coins. Backup! Backup! Backup your wallet.dat file or private key so you can import them into the latest version of the client.
- Be warned that unless you’re running Core (aka QT), you could have issues with wallets containing lots of UTXOs (Unspent Transaction Outputs - Where your coins REALLY live). Go read the ELI5 below, and keep a close eye on your transaction counts. If you DO run Core, realise that all full clients, regardless of the coin, require a copy of the blockchain and must keep it up to date. This will cost you time, storage space and bandwidth. You can save a little by downloading the bootstrap file though. I haven’t checked how recent this one is, so let me know if you find a more current version.
Bootstrap file for Core to save some download time.
Dogecoin Core Guide Wiki
MultiDoge v0.1.7 2016-Jan-31
Android Dogecoin Wallet 2.0.8 2016-Jan-18
Android Coinomi Wallet
Java Cate 0.14 alpha 2 Multicoin wallet 2016-Feb-14
Exodus multicoin wallet
Do you REALLY need a client?
- Probably not, if truth be told. Go read these two ELI5’s if you haven’t already. They contain critical information to help you decide. I’ll wait till you get back. ;)
Paper Wallet Generator
- OK, so next, grab this wallet generator. Even if you plan on running a client(s). Because a) it does many, many cryptocurrencies, and b) you WILL need wallets at some stage over and above what you keep in your clients. Just be sure to run it locally (and offline if you’re truly paranoid).
Sample HTML Wallet List
- Oh, and here’s a simple way to keep track of all your wallets using HTML. You can grab the source and modify it, then upload it wherever you need to suit your needs. You will also want a separate file with your private keys, but don’t upload that one anywhere, because if you lose your keys or someone else gets access to them, you will lose your coins.
Dogetipbot subreddit and website
- Next, be aware that there are online wallets available. While any wallet you don’t own the keys to isn’t actually yours, and therefore isn’t safe, the following are safer than most. Dogetipbot of course is used daily by shibes on Reddit. Block.io uses multisig and gives you Doge, BTC and LTC wallets as well as testnets, and Dogechain gives you your private keys (and also offers a wallet sweeping service).
- Exchanges also offer wallets, of course. Not that you should use them to store your hard-earned coins, because they can and do get hacked with monotonous regularity. But at some stage you’re going to want to trade, or hold a few uncommon coins. You could do worse than these three:
ShapeShift - Not really an exchange, rather a currency trader.
- And then there’s the obligatory question of mining. Put simply, mining is for all intents and purposes dead, and has been for a long time now. The costs are greater than any possible returns. But, if you insist on doing it anyway, maybe because you inherited a miner, you can earn about 0.01 LTC/day per MH/s merge-mining at Litecoinpool. That’s about 4 cents. :(
Explorers BitInfoCharts - My favourite, has charts!
/dogecoindev where the devs hang out
- Shibes sometimes complain that the devs are not as active in /dogecoin as they used to be. You can find them on IRC, slack or their very own sub if you need them though. Or poke sporklin, who can often help.
- You can of course ask any questions here, or post them in the sub. However, do try searching first, because I guarantee every possible question has been asked many times before. And you should also subscribe and hang out in /dogeducation occasionally. There’s much awesomeness there.
Preev currency value calculator
EDITS: From peoplma
I was wondering if you could add just a couple things. A link to the coinomi android wallet, it's probably the best one out there. And a sentence somewhere along the lines of "if you need help with any dogecoin software you are welcome to make a post, but PLEASE include your OS, version number of the client, and any relevant transaction IDs that you are willing to share" if you can fit that in somewhere.
Also, if you want to link to Prohashing, I'm pretty sure it's the only Scrypt mining pool that will actually pay out in doge. The others I know of pay out in litecoin or bitcoin. And it's a profit switching multipool, so gives a better return than just mining ltc/doge.
And there's these two wiki articles I thought would be helpful to link /dogecoin/wiki/technical for those technically minded newbies or intermediate users who want to dig a little deeper. And maybe a link to /dogecoin/wiki/dogecoincoreguide next to the link for dogecoin core.
Finally a proper sticky post! Here's some other stuff you could add:
zpool.ca mining pool - You can get paid in pretty much any coin, and you can mine in multiple algos (currently mining lyra2v2 with my GPU). Doing about 500Ð/day
shapeshift.io exchange - My favourite exchange, quick and easy. No registration required!
Also, you should add some blockchain explorers!
chain.so - Support for bitcoin, litecoin and doge.
dogechain.info - Official blockchain explorer. Includes a wallet (already mentioned). Live update currently not working (?)
EDIT: Here's another thing I found!
preev.com currency value calculator - Easy way to check the value of your dogecoins (or bitcoins, or litecoins, or peercoins)!
Useful Beginner's Guide to Syscoin
submitted by idbrews to SysCoin [link] [comments]
What is Syscoin?
Some have described Syscoin (SYS) as the Shopify, Amazon and Ebay of the blockchain world. Syscoin is a revolutionary cryptocurrency that offers near zero cost financial transactions, incredible speed and provides businesses the infrastructure to trade goods, assets, digital certificates and data securely. Syscoin isn’t just about money and trading, it has the ability to attract various business types thanks to its native set of features geared towards business on the blockchain. From eBay traders and High Street shops to Medical applications, Insurance and Gaming, Syscoin’s decentralized network benefits everyone! Syscoin is developed by Blockchain Foundry (BF). BF provides blockchain technology based services, projects and products for a wide variety of use cases with the stated aim of disrupting markets by leveraging the potential of blockchain technology. Syscoin is mainly known to be the first cryptocurrency to offer a fully decentralized marketplace based on blockchain. What is lesser known is that this is only a part of what Syscoin offers. With the introduction of Masternodes in February or March 2018 SYS will be transformed from just a ’marketplace coin’ to a completely ‘utilitarian coin’. The Masternode infrastructure allows the addition of decentralized databases and file storage, increased transaction speed to surpass POS/Visa/Mastercard capabilities, true Turing complete smart contract capabilities for unlimited business logic, sidechains, application layers and an identity layer. This will all be accessible through an API, rather than a new language, enabling nearly any developer to create any blockchain application they can conceive. This will usher in the next generation of blockchain applications - made for new or existing businesses - by conveniently offering everything available from the blockchain space today. In simple terms think Dash + Ethereum/Lisk + Monero + Nano + Storj + Particl capabilities all in one coin!
The blockchain as conceptualized by Satoshi Nakamoto back in 2008 envisioned a peer-to-peer electronic cash network that would prevent double-spending. A year later, the blockchain became an integral part of bitcoin, serving as the latter's public ledger of transactions. Although Nakamoto's reference client mentioned a decentralized marketplace service, the subsequent implementation did not incorporate this due to a lack of resources. Syscoin was initially described in a 2014 draft whitepaper that envisioned Decentralized Marketplace Creation, Decentralized Smart Contracts and Documents, Decentralized Certificate Issuance and Transfer, and Decentralized Data Storage and Retrieval, as among the services that it would offer upon its release. Syscoin aimed to bring Nakamoto's vision of a decentralized marketplace back into the blockchain, among the other commercial-grade services it aims to deliver to clients. Other services that Syscoin plans to provide include secure data storage and transfer, and unique user aliases that link their owners to the services controlled by the alias. The early Syscoin wallet was superseded by the release of Blockmarket Desktop 1.0 on September 12, 2017, marking the culmination of Syscoin's vision of a fully decentralized marketplace with a desktop GUI based on the blockchain. The planned release of Blockmarket Web, a fully web-based version, and Blockmarket Professional in 2018 takes that vision one step further, as more advanced seller stores become a reality.
The Team The Team that NEVER quits!
Before the launch of Syscoin (Q3 2014), there was a presale ICO by Moolah (as a partner), which turned out to be detrimental for Syscoin. The project raised around 1,000BTC for development but the Syscoin Team only managed to access 250BTC which were used for price support. Moolah (Ryan Kennedy) absconded with the bulk of the ICO funds and the Syscoin team were left with ~30million Syscoin at a price around 400 satoshi. Even after this tragic event, the devs didn’t quit and continued to work on the project without stopping. The case against Moolah is still on-going. See the article from CoinDesk here: http://www.coindesk.com/uk-court-syscoin-injunction-moolah-750-btc/
. What is this detail telling us about the dev team? While some crypto projects are just scams and bring little to no innovation, they’ve proven that they are in it for the long term - ably demonstrated by the fact that they continued to work despite their funds being stolen. And now that hard work is beginning to pay off with the entire team going full-time for the first time in January 2018 and new developers being hired following VC funding for BF. View Team Page.
Blockchain Foundry Products BF Products
What is Blockmarket Desktop?
Building on the World's First Decentralized Marketplace, Blockmarket is the newest generation of Syscoin's Desktop wallet with a complete, state-of-the-art marketplace built-in where you can securely and reliably buy and sell any items you wish. Entire stores can be created directly through the marketplace where you can sell your own products or re-sell others’ products for commission. Use of blockchain technology eliminates middlemen, credit card fees, maintenance fees, downtime and political interference. Persons are literally able to buy or sell anything to anyone, anytime, anywhere on Earth!
Blockmarket Desktop was launched on September 12, 2017. Download Blockmarket Desktop 1.2
Key Blockmarket Features
- Decentralized Marketplace
The marketplace platform provides a decentralized and high redundant channel for selling goods and services. Features include: • Price Pegging to currencies such as USD, EUR, GBP, CAD, CNY and BTC • Bitcoin and Zcash as payment options • Arbitrated Escrow • Encrypted Messaging • KYC/AML Compliance • Images • Unlimited Inventory Items
- Name Aliases
Wallet addresses for cryptocurrencies generally consist of a unique string of between 27-34 alphanumeric characters. Such an address isn’t easy to memorize. Although the addresses can be added to an address book within the wallet, Syscoin has taken the user's convenience one step further, allowing you to create a unique Alias for your wallet address, such as a name, title, or characters specific to a username. These can be used to send SYS from home, to a mobile wallet, to work, to friends, to common suppliers or to repeat customers easily, without requiring any memorizing, writing it down, copy & pasting or emailing yourself the address.
- Digital Certificates
Using the cryptography of the blockchain persons can issue, authorize, and exchange digital certificates of any kind. With Syscoin anyone can issue provably-unique certificates with text or ASCII content to one or multiple parties on the Syscoin blockchain. These certificates can be authenticated by anyone via Syscoin’s cryptographic proof of work. This allows for the creation and free exchange of any kind of digital asset such as ownership certificates, warranties, receipts, tickets, certifications, diplomas, software licenses and more.
- Integrated Exchanges
Integrated Crypto exchanges - Flypme and Changelly will facilitate exchanging 30+ cryptos for SYS, directly within the Blockmarket wallet.
- Security Audit Verified
Blockmarket was successfully and independently security audited by Digital Boundary Group and was deemed low risk. View Audit Results.
Blockmarket Desktop – Quickstart Tutorials (16 short vids) BM Desktop – Quickstart Tutorials
Blockmarket Web – (The Key to Mass Adoption)
BM web will bring SYS’s existing decentralized marketplace and all its features into a web-based version, enabling ease of use with a simple email and password login (grandma friendly) without any need for downloading a wallet or waiting for sync. Blockmarket web will be launched in Q1 2018. This launch will be accompanied by a marketing campaign roll-out that seeks to build brand recognition with audiences within the existing crypto ecosystem and more significantly with the broader, global, non-crypto audience. For this reason Ballistic Arts, a full-service marketing agency was retained by BF. BF Engages Marketing Agency
Primary Target Market + Value Potential
The primary target market for BF’s Syscoin/Blockmarket web flagship is the retail e-commerce industry. This sets up their decentralized marketplace to rival such commercial giants as Amazon ($648B market cap), Alibaba ($453B market cap) and eBay ($43B market cap). According to eMarketer’s Worldwide Retail and Ecommerce Sales report, global retail e-commerce sales for 2017 were $2.3 Trillion. This is expected to reach an estimated $4 Trillion by 2020 reflecting the rapid growth within this sector. To perform a very simple assessment of the Syscoin/Blockmarket web’s potential let’s assume that a 1% portion of the forecasted $4 trillion market is captured, which represents $40 billion in revenue. Assuming a sales to market cap ratio of 1:1 for simplicity, the circulating supply of 531 million SYS, with a $40 billion market cap yields a price of roughly $75 per coin. However, with masternodes that limit the circulating supply and token utility that extends beyond retail e-commerce, the SYS price could likely reach much higher. Please note that these are just very simple assumptions and projections for this exercise, however the real world driven potential that this project has is clearly evident.
Key Syscoin Developments
- Z-DAG: Zero Confirmation Transactions with Double Spend Protection (WORLD’S FIRST) View Developer’s Twitter post View Syscoin’s Twitter post
- Masternodes Ability for world-class transactions-per-second performance to scale-out with added nodes (theoretically 100k TPS per 1000 Masternodes, 300k TPS/3k masternodes, etc).
In later releases, masternodes will also process smart contracts and facilitate sharded+encrypted offchain file-storage (with onchain anchors), among other touted functionality. They should also result in steadying the price movements - less volatility as holding will be incentivized.
- Masternode Rewards + Min. Hardware Specs Masternode Rewards + Min. Hardware Specs Masternode ROI Calculator
- Smart Contracts
Scalable Ethereum Virtual Machine: Allows Turin complete smart contracts to be executed following the ethereum protocol at a much faster speed and at a fraction of the ethereum gas price.
- Assets & Token Issuance
With its token issuance service, Syscoin allows anyone to create a custom asset token which can then be sent directly to anyone else on the network. This facilitates a variety of use cases including ICO token issuance, supply chain management, reward points, and loyalty programs.
- Anonymous Transactions
Anonymous transactions: via mixing/shuffling at user-specified denomination. Afterwards, additional tech will be added in the near future which will further compound the degree of anonymity provided -Add ValueShuffle running on top of the masternode layer and you have the world's most advanced privacy tech in any coin.
This brings true money fungibility to Syscoin and the missing link for true economic sovereignty. View Developer’s Twitter post.
- Instant Send
Transactions can be sent and received instantly. This represents a similar sending capability as Dash, but is a step beyond- A type of backend node locking will allow an instantly received sum to be sent immediately, without delay, and without network risk of double-spend.
Why Invest in Syscoin?
Merchants Merchant Pilot Program
White Paper White Paper.pdf
Note: It is anticipated that the whitepaper will be updated by the team in the near future due to recent developments
Roadmap Roadmap 2017-2018.png
Blockchain Application Development Architecture Blockchain Application Development Architecture.png
Feature List 2017 & 2018 Feature List 2017 & 2018.jpg
Where to Buy
• Tux Exchange
• Block Market Wallet 1.2 – Windows and Mac. Download from https://syscoin.org/
• QT Wallet for Developers: Download from https://github.com/syscoin/syscoin2/releases/tag/2.1.6
• Coinomi – Syscoin MultiCoin Wallet (only supports send/receive)
• HolyTransaction – Syscoin Multicoin Web Wallet (desktop & android)
Need Help or Want to Contribute?
If you need help for an important wallet issue or if you want to know how you can contribute in promoting Syscoin Join the Slack channel
where the SYS team and community members are active, helpful and responsive.
- SYS Team - keyare, sidhujag, sebastien123
- Redditor alias - djminger007
- Redditor alias – Todoruku
- Twitter alias – CryptoMink
- Medium blogger – Steven Voros
- Medium blogger – Daniel Westby
- Medium blogger – The Crypto Journal
- Slack Community members – Redrace, Mettamark, Rare and Viljis
Other Sources https://syscoin.org/ https://twitter.com/syscoin https://www.blockchainfoundry.co/ https://en.wikipedia.org/wiki/Syscoin
This post was last updated on Feb 10 2018.
This post was created particularly to aid those who are new to Syscoin. Please note that the content provided within this post is for information purposes only and is not to be construed as investment advice.
#7821 4226aac init: allow shutdown during ‘Activating best chain…’ (laanwj) #7835 46898e7 Version 2 transactions remain non-standard until CSV activates (sdaftuar) Build system #7487 00d57b4 Workaround Travis-side CI issues (luke-jr) #7606 a10da9a No need to set -L and –location for curl (MarcoFalke) Bitcoin-qt v0.11.1 and now v0.11.2rc1 32 bit Windows, running on Win7 with 2GB ram. At app startup, the splash screen runs through verifying and rescanning status messages fairly quickly, then gets "stuck" showing "Activating best chain"... Running bitcoin-qt v0.11.2 I run into "Activating best chain…" with high CPU load for 20 minutes on slow machine. Not sure if relevant: I wanted to "quickly" do a transaction but 0.11.1 crashed, making a re-index necessary. I downloaded 0.11.2 meanwhile, orderly interrupted the re-index to let the latest version take over after 10% progress. #6104 3e2559c Show an init message while activating best chain #6125 351f73e Clean up parsing of bool command line args #5964 b4c219b Lightweight task scheduler #6116 30dc3c1 [OSX] rename Bitcoin-Qt.app to Bitcoin-Core.app #6168 b3024f0 contrib/linearize: Support linearization of testnet blocks Bitcoin Core 0.12.1. Bitcoin Core installation binaries can be downloaded from bitcoincore.org and the source-code is available from the Bitcoin Core source repository.. Bitcoin Core version 0.12.1 is now available from: