https://github.com/gridcoin-community/Gridcoin-Research/releases/tag/188.8.131.52 submitted by
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
[184.108.40.206] 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)
This is general advice and my opinions They are based on many years of experience. ... and to be CLEAR, I am in no way affiliated with any of the sites running today or mentioned here. I don't make ANY money from them... I could care less if you take the advice or shit all over it. This is not an advertisement for any one site... It is my opinions based on my experiences in this industry. I have made a LOT of money in the industry, and made a lot of other people a lot of money. There are good and bad things about every site out there, some I recommend here, others I will shit on, but I make nothing, own nothing, am not affiliated with any of them.
I have often been asked a LOT of questions by people looking for advertising and website help. I decided this was the best way to answer all the questions and help the community.
I hope you can learn something from this that helps you as you advertise or even better keeps you safe..
I worked for backpage for a long time, I helped start the bitcoin payment side of the site, I also helped start one of the backpage replacements. I have consulted on 2 other clone site startups, and to top it all off.. I owned a escort agency on the east coast from 2003 to 2011.
I owned my agency with 2 partners, I kinda fell into it. They needed computer help, I was a computer and marketing guy.
SO through all of that I am pretty sure I know a LOT about advertising for sex workers and the industry in general.
For Escorts and sexworkers things are very different in today’s post backpage.com and SESTA/FOSTA world. These changes and new laws are having serious effects on advertising adult services.
Here are a list of things to consider: Many of us remember Escorts.com, and Craigslist. Those were really the only places a SWr needed advertise. A simple $5 ad on Craiglsist could make an advertisers phone ring for days. A single ad on escorts.com could fill a schedule for weeks. Then Eros got big, it became as good if not better than escorts.com quickly, most often attracting the most quality clients.
Our Agency's used all 3, escorts., eros. and CL. At the time backpage was a shit site we didn't bother with... there were a FEW other sites we listed links to our own websites on, like southerngfe.com or openadultdirectory.com and a few others... more for SEO than anything else... they didn't bring much.. CL was all we needed. ECCIE was not big at all in our region then, so we never really used them.
Then it all started to change… CL took down the Adult services section. Escorts.com was raided and shuttered.
Backpage became king. I remember people paying just .25 cents to post an ad for a week on BP, then just days after CL closed it was $3? I had started working for Village Voice by then as a consultant, and was there when CL closed...
I got calls from my partners... usually by 1pm we had booked a few calls in each city (we were in 3) and had taken several dozen calls asking prices... we had booked ZERO that day and taken less than 5 calls... ALL from our website and google searches... our CL ads had not made phones ring once... they kept testing the phones... they all worked.
Then word came through from my office at BP that CL had pulled the plug... they put a big "CENSORED" label over the adult services tab... a few days later it was gone.
After the smoke cleared, there was only a few places you really needed to be on... cityguidex.com, eros.com, ECCIE (in certain regions) and backpage. That was it.
THere were a few other sites... and they were more regional... this is 2010/2011 I am talking about...
The only place a escort REALLY needed to post an ad was backpage… if another site popped up, the rule of thumb was simple… if no other SW’s are posting there… don’t bother… its not worth it.
Now lets be honest.. there are advertisers that could make a very nice living and book a lot of calls from just backpage... and there are the ones that would never could never... These were advertisers that had their own sites, charged upwards of 500/hr and did the fly me to you type stuff...
very few advertisers doing 150h/h calls off backpage have websites... we all know what I am talking about if you have been around at all.
During this time for the most part , Agency's in most citys started going out of business...
this was for a few reasons... 1. the yellow pages DIED! Smart phones KILLED the yellow pages. NO ONE USES A PHONE BOOK ANYMORE!! It cost a min of $10k up front to put even a small ad in the yellow pages... the agency's that could and did had ruled the escort world since the 80's... if you were a sexworker you worked for an agency because you couldn't get calls otherwise...(generally speaking)
suddenly CL and other sites like it made it so ANYone with a cell phone could run their own agency, or even better, go "independent"
And the indys and the independents and the internet sites like CL and backpage killed the agency's.
Clients looked at the math like this... lets say an agency charged $200/hr... the girl was usually getting a 50/50 split, so she took 100. They would then "charge" a tip of an avg of $100... so the girl got 200, the agency 100.. and the guy was out 300... but that same girl could post an ad saying 175/hr with NO upsell... and although yea... she made 25 less... she would book 10 times the calls and not have to split shit... guys wanted to deal direct to save and get more "bang" for their buck.. (pardon the pun)
So the internet was suddenly swamped with independents... at about the same time CL was king and then died... it was a crazy time... suddenly all these independents need a place to advertise, because its back to the agency's (pimps in a lot of cases) if they cant get calls... very few were gonna start their own websites, and if they did... how do they drive traffic? Backpage filled the void. ECCIE grew as did a few other sites
Again, I was working with them by now... and it was retarded. "Craigslist alternative" was one of the top google searched terms in the WORLD in sept 2010 when CL closed... think about that.
Of course BP starts charging more... and more... and more. They offered more features.. charging for all of them... and now it was a crazier time... all the other sites are either crap or being shut down. Eros was super expensive, and wanted your DL licence and more...
SO BP was king! But we all remember how that went... and come April of 2018.. BP is gone, and then the real shitshow started.
Bedpage.com, Onebackapge.com, Ibackpage.com Ebackpage.com backpage.cl the site I helped start with the backpagecredits.com guys was yesbackpage.com, then skipthegames.com cityguidex.com slixa.com tryst.link there was some gator site out of Australia, afterdarkads.com, eros.com had a knock off.. DOZENS of sites and I cant remember how many others have popped up and died in the past year... its been insane. I consulted on afterdarkads.com for payment systems, and they are doing great. Others are dying. ECCIE is doing better than ever
And ALL of the rules you thought you knew about advertising are gone.
Since the demise of backpage, there are literally dozens of sites popping up all jockeying to be the next backpage. The truth is… it will never happen. Some will have more success than others, some will fold, some will remain… but the new reality is there are now be dozens of places to advertise. I helped the girl making verified vixens... she has already shut down for a few months because she is underfunded and cant market the site right. (she says she will be back... it was a GREAT site)
The rule of thumb was that if you saw a site that you could advertise on, and there was no one else in your city/region... dont bother. ESPECIALLY if you had to pay...
So now, when you find a new site, and there is just a few ads you figure are fake there… should you ignore it and move on?
NO! advertising today is a different animal. An advertiser needs to have as many ads up in as many places as possible… and most importantly, needs to think and act like a client.
We here in the industry knew an hour after backpage closed… we were searching for alternatives immediately. There are clients out there that look for an escort maybe 1 time a year on vacation, or the guy that found his regular SW’r on backpage 2 years ago… and now is looking for a new one… they are searching for “backpage alternative” or “backpage replacement” (according to google analytics those are the TOP search terms related to sex work and backpage since April 2018) they are searching craiglslist personals replacement, or "new backpage" ...
You need to be on the sites that come up in those results, EVEN IF THERE IS NO ONE ELSE SMART ENOUGH TO POST AN AD THERE!!! The clients are searching using those terms…and dozens of others, and they are browsing the links they find… and they are not finding you! Why is that? You are not thinking like a client… you found bedpage… saw there was a ton of ads… and figured that if everyone else is posting there… I should as well. Bedpage used a bot to crawl backpage in the weeks before it closed, and copy/pasted the majority of ads it found to bedpage… MANY advertisers report getting calls and finding their ads posted on bedpage… and they did not create an account or post. MOST of the ads you are PAYING to compete with are fake... clients know it.. they are moving on from those sites FAST.
Sites like bedpage use to be having lots of success… they had a LOT of posts, and word got around to advertisers fast… BUT THE CLIENTS DIDN’T GET THE WORD! Yes, dedicated sex mongers that search for escorts daily know… and the guys that spend time on the boards and in forums know.. but the MAJORITY of clients are the guys that MIGHT call one or 2 times a year… they have never heard of usasexguide.nl or the otherboards.com… they are doing something simple… typing in backpage… finding its gone… then going to google, and typing “backpage alternative”.
And here is the next issue, Bedpage, ebackpage, ibackpage, yesbackpage… they all have a similar problem, they attract the WORST customers. The calls and texts looking for a $50 blow and go all come from sites like them. The guys that DO crawl through the dozens and dozens of fake ads end up just blasting texts to every phone they find (even tho you said no texts in the ad) 3 am msgs that say "hey" or even worse.. "blow me in my car for 50$" after demanding pics to "prove" you are real...
Advertisers today need to get on as many sites as they can. Get on all of them... ESPECIALLY the ones with hardly any ads. The unfortunate byproduct will be you will get those shitty messages.. part of the price you must pay for being in this industry...
Here is why: 1. Branding... Most of these clients are searching on dozens of sites for an escort... if they see you on afterdarkads.com, AND on tryst, AND then on eros., then AGAIN when they kick back to afterdarkads.com, AND then AGAIN when they find slixa.com ... and THEN they FINALLY decide to book.. was it really the ad on slixa that really did it? Or the fact they saw you everyplace and it helped him know you are real, not a fake ad? Was it the ease of finding your ad on a site like afterdarkads.com because they only had to sort through 5 or 6 ads? What was it that made him book? Do you REALLY think having just ONE ad on bedpage, because that's where everyone posts is the best idea? It was because he saw you over and over he was BRANDED and eventually booked.
Branding is this, what do you clean your ears with? NO, not q-tips... its a cotton swab, you have been branded. WHat do you blow your nose with? NO, not kleenex... its a tissue... you are branded. Whats "The best part of wake-ing up.......? its WHAT in your cup... yea.. its coffee.. but you just said Folgers... BRANDING... get in front of ALL the clients as often as possible... BRAND them to think of you when they think of an escort.
The MAJORITY of clients are searching for an escort or hire escorts just a few times a year... they have never heard of all these sites the way we have... a few years ago 1 ad on one site was all you needed... now escorts need 30 ads on 10 sites. Its the way it is.
- Simple odds... there are 20+ new sites online... if you are on just 3 of them.. what are your odds that perfect client looking for a girl/guy just like you finds you? Be on all 20 and your odds are much better. There are plenty of clients seeking a sexworker or escort that are only finding escort sites like afterdarkads.com or slixa.com , etc right now for the first time... and in most cities there are just 1 or 2 ads... the bigger cities a few more... if you posted a free ad on there last week.. that you didn't even need bump or pay to feature... he WILL find you... BUT, if you are not there... he will end up moving on, maybe even searching a dozen other sites with barley any posts... maybe give up, search for an agency... go to a strip club book your competition.. who knows. What I DO know is that every time you post an ad on another site... you increase your odds dramatically that you are found. REMEMBER, these clients don't know all the sites... who knows what site they will end up on. And if you are NOT on the ones they find.. there is 1000% chance they call you.
A great way to booking more is to get a website. There are a lot of VERY inexpensive ways to post one.. many advertisers cant or don't have the resources or ability's... be very careful with the services promising escort websites for money.
I am happy to walk you through some easy free steps that can get you on the right path, I will also build a simple free site, just cover the cost, The hosting I recommend will cost you about $10/month, the domain registration and privacy will be about $25 a year, for under $50 I will put a basic site online for you , and show you how to modify it and post to it form your phone. I want nothing for it... I am happy to help anyone in this industry. just PM me. Once you have one.. .LIST YOUR ESCORT WEBSITE ON ALL THE ESCORT SITES!
Another thing to beware of, MANY reports claim that bedpage, aka ebackpage, aka, ibackpage, aka, onebackpage, aka icracker aka yesbackpage (all the same few guys in India and Bangladesh) have all been known to of given access to advertiser accounts to law enforcement resulting in several arrests. Escorts in NY, TX, and Co all report the same thing, when they were arrested, LE had access to their ad account, showing IP’s they posted from (leading one agency to the actual incall location they also posted ads from) payment methods and more. Be CAREFUL with what you post... use a VPN,
do NOT use any payment method that can be connected to you, Tryst has a secure system it looks like and you can use btc or gift cards. Most of the other sites accepting credit/debit cards are at risk... if you are paying with a CC, GET A GIFT CARD like vanilla visa and pay cash for it... afterdarkads.com uses a payment site called adacredits.com and allows payment via many ways that hide your identity like gift cards, Bedpage does something similar but I worry its out of india... but do NOT use your personal amazon acct to buy an amazon card to buy credits from any escort advertisement site. Don't use your CC to buy a best buy card or target card to get an ad on bedpage. . If a site is asking for you to use a debit credit card, or worse upload an ID as proof of anything, you are taking a HUGE risk. eventually a lot of these sites are gonna get raided or closed. or hacked... ( I see rumors yesbackpage just got hacked by one of the owner siddiqs little jerkoff programmers thiefs... lol) whatever info they have stored is all sitting there waiting to be exploited. BE CAREFUL
Use a VPN... ALWAYS. If you cant, get a burner smart phone from Walmart through straight talk.. DO NOT sign into your personal FB on that phone, or your reg email... you want that phone and everything on it to NEVER have any attachment to who you are. pay cash for it all and to reup monthly. INSTALL A VPN if you can. Ask for help here on how to do it.. your safety and freedom depend on this.
Its not just the gov you are hiding from... its clients that have tech backgrounds. I will promise you.. there are VERY few advertisers out there, that if I wanted to, I could get your real name, address, phone, birth-date, and MUCH more. There are THOUSANDS of people out there like me... Laugh if you want but its true. At least I am a decent guy, I don't see sexworkers myself, not that I find anything wrong with it at all.. I am safe, you dont need worry about me, But we all know there are PLENTY of weirdos out there that will stalk you, harass you, and then there are the ones that want to hurt you. Yea, the gov will use your information to arrest you or fuck with you... but those scumbags are killers that will rape you and stick you in a dumpster... BE CAREFUL. BE SAFE. BE SMART.
YOU NEED TO BE ADVERTISING A LOT AND OFTEN!!! Those days of 1 ad producing tons of results are OVER… unless backpage returns… you need to be posting a LOT… it is the new world we live in!! On MANY sites! tryst.link is a top result and is working hard to bring the traffic, they seem to care about advertisers. slixa is a great site but not a lot of results. you know the deal with most of the older backpage clones like bedpage. skip the games is REALLY solid. As I said I helped the girls that started afterdarkads.com
, they like tryst care, are sexworkers themselves, and verify advertisers... you are not competing to post against fake ads on afterdarkads. They are doing a great job. Cityxguide is solid for the most part I can see, I hear that on the west coast they are killing it. There were a few guys from BP that went to work for them, I hear good things... You need to be on ALL of them and posting a LOT!! post 1 ad per day on EVERY single site that has daily posting EVEN IF YOU JUST POSTED THE ONLY AD YESTERDAY!!!! on sites like tryst with a profile, at a minimum 1 profile, its smart to have a second with dif pics and numbers... pics hiding a face, diff description... in one describe yourself as a sexy cute fun playful thing.. in the other describe yourself as a dominant sex machine... As sexworkers the best bet is to be a chameleon and adapt yourself to what the client is looking to pay for...
HAVE A SCREENING PROCESS!!! Most high end advertisers with their own websites have extensive screening processes... go find them, read their requirements... what will work for you? Mimic them.
Advertising after backpage is not as easy as it once was… it takes work… it takes INVESTING in yourself. EVERY dollar you spend advertising is an investment. Not enough money in your pocket? INVEST MORE!
I hope you get something that helps you from this. It is all my opinions based on many years in this industry and seeing a lot. I was very successful advertising my own agency and learned a lot. I am happy to answer any questions I can. PM or ask away here! Again PLEASE, be careful and be safe!
Dev meeting? Would say so, yes The people are still exhausted from the payment ID meeting :) Guess we could ping some people vtnerd, moneromooo, hyc, gingeropolous, TheCharlatan, sarang, suraeNoether, jtgrassie Anyone up for a meeting? Yep I'm here Here o/ Perhaps we should just start and people will eventually hop in? oof sorry guys, I'm working on the new FFS and I forgot all about this. Got a couple of new volunteers. This literally might be able to launch tomorrow. I know that. It's called "flow" :) I could run if you're out of time? go for it dEBRUYNE you guys are going to like this new FFS. We're like 99% done. Hi rehrar: someone else do the milestone thing already? All right, jtgrassie, perhaps you'd to start w/ briefly describing your most recent PR? https://github.com/monero-project/monero/pull/5091 oneiric, xiphon did everything like....everything As far as I can see, it allows the user to push his transaction over I2P, thereby masking the origin IP of the sendeuser great And it hooks into vtnerd's PR right? Sure. It basically just builds on vtnerds Tor stuff. sorry dEBRUYNE Really not much added. I have it running and tested. From the perspective of the user, what needs to be configured exactly? Nice Assuming the PR is included in the release binaries I'm using knacccs i2p-zero duirng testing but will of course work with any i2p setup sorry dEBRUYNE <= Np Looks a little like dams breaking, now that we have some dark clouds over Kovri and people take matters into their own hands ... User needs to run i2p, expose a socks service and and inbound tunnel. Basically same as Tor Okay, so should be reasonable as long as we write proper documentation for it (e.g. an elaborate guide) rbrunner, yes, knaccc credit for jumping on i2p-zero really dEBRUYNE: documentation monero side is kindof done. i2p side is very much implementation specific. I suppose we could write some guides for the most popular implementations? e.g. i2p-zero aims to be zero conf, but i2pd or Kovri would be differnet. I see, great vtnerd___: Do you want to add anything? could amend the current kovri guide for monero use from --exclusive-peer to the new proxy support Now I have i2p-zero running and tested with the #5091, I plan to jump back over to helping knaccc on getting that polished. I added support for socks proxy in the basic wallets ^ excellent Yes vtnerd___ I havent tested it yet but looks sweet. So connections to `monerod` over Toi2p are possible within wallet cli and wallet rpc Awesome This also implies auth+encryption even if ssl is not in use (when using an onion or i2p address) All right moneromooo: are you here? If so, could you perhaps share what you've been working on? I am. I revived the SSL PR, more stuff on multi sender txes, an implementation of ArticMine's new block size algorithm. I presume a multi sender tx works similar to multisig insofar as the senders have to exchange data before the transaction can be performed right? Yes. There are 2 SSL PRs. What's the diff? Theoretically this would also allow the sender to provide an output right? Which would be kind of similar to Bitcoin's P2EP The second one adds some things like selecting a cert by fingerprint. Yes. (for the first sentence) All right, awesome For anyone reading, this breaks the assumption of the inputs belonging to a single sender, which makes analysis more difficult Nice side-effect. Much work coming for the various wallets to support that rbrunner: Anything you'd like to share in the meeting btw? Yes, just a little info I have started to seriously investigate what it would mean to integrate Monero into OpenBazaar I have already talked with 2 of their devs, was very interesting In maybe 2 or 3 weeks I intend to write a report Too early to tell much more :) Soon^tm I guess :) Yep Currently wrestling with Go debugging whole new world moneromooo: Has pony recently shared any insights regarding the upcoming 0.14 release btw? No. All right I would love to see the tor & i2p PR's merged sooner rather than later so we can get more testing done. ^ +1 Isn't that famous early code freeze already on the horizon? fluffypony, luigi1111 ^ I suppose I could provide a little update regarding the GUI btw As always, lots of bug fixes and improvements :-P selsta has recently added a feature to support multi accounts dsc_ has revamped the wizard and will now start working on implementing the different modes and a white theme dsc_ is working fulltime on the GUI already? yes :) dsc_ is bae In light of the recent payment ID discussion, we've also, by default, disabled the option to add a payment ID unless the user explicitely activates the option on the settings page rehrar ^ nice I spoke about this yesterday at the coffee chat, this is not a good decision. How does it handle integrated addresses? The same way? rehrar ? For the next many months, we are still stuck with PAyment IDs in the ecosystem. Making it harder for people to access them will make Monero suck so hard to use for the average person for many months. i agree with rehrar Remove the option of Payment IDs when we remove Payment IDs rehrar: The new GUI release won't be live until probably mid march though Which is a few weeks in advance of the scheduled protocol upgrade Payment ID removal comes in October right, but Payment IDs are not removed in March Did we not have loose consensus on removing the old, unencrypted payment IDs in march? they are removed in October We had discussed a deprecation in March and a ban in October ok, then if we are going to do that, we have to commit to it and contact the exchanges like Binance that use them and get rid of them in the next few months (of unencrypted) Binance is huge, and if they still use them, then people will be very upset that they can't deposit or use Payment IDs easily I'm just speaking from a UX perspective. I thought it was unencrypted in April and possibly encrypted in October Yes I do agree Timeline and notes: https://github.com/monero-project/meta/issues/299 impossible to remove them for march, many exchanges still use them We can defer it to the 0.15 release if needed Well, that wasn't the impression for them log that I just read today This was all discussed in the earlier meeting linked above We have to force the ecosystem off of Payment IDs before we remove them from the UI, is all I'm saying Remove != make difficult to use ... or make them more difficult there, right? ping sgp_ sarang, I understand, and I agreed with you during that meeting. But then I started thinking of it as a UX person, which I am. And that huge massive problem leapt out at me i think making them difficult to generate is a good idea but making them difficult to consume and use is a bad idea well, maybe not a good idea, but a better idea ^ If we defer the decision to depriciate long payment IDs to october, won't we have the same issue then? The UI can gave an expandable payment ID field like MyMonero and we can still call it deprecated It is foolhardy to remove an option that the ecosystem uses. So I suggest we keep the Payment ID in the UI until October when they are completely banned. no dEBRYUNE, because they will be banned via consensus sgp_ imo it may be a misdirection of dev resources to add that since things are proceeding in the short term rather than long term but this is a relatively minor point Nothing matters til exchanges change All right The issue is that consensus will still have them in April, and exchanges won't upgrade because they are still allowed. Thus they must still be in the UI. endogenic these changes are already merged in the GUI to hide it like you do ok But when they are banned, exchanges are forced to upgrade or stop using Monero, so we can remove them safely because they won't be in use rehrar: that's a strong assumption sarang that they will upgrade? yes if they don't, then they can't use Monero If exchanges require pid, users need a way to set a pid. Making it hard for the user in the interim is just going to be a nightmare. we have decided to take our "stand" in October A way that is not too hard, then To be clear, we still intend to deprecate long encrypted payment IDs in April right? But no enforcement until October the term "deprecated" doesn't mean much if it's still allowed, and used in popular places yes, as far as I understand it jtgrassie, exactly True I suppose dEBRUYNE: we need to be more specific when talking about deprecation the person who suffers is the user There are two proposals for GUI deprecation: 1. Hide it in the send screen with a simple option to expand (currently merged iirc) 2. Hide it completely in the send screen unless users enable the field in advanced settings (PR'd but not merged yet iirc) What are the arguments for 2? Both are poor options, but 1 is better than 2 by a long shot Well the people who need to be made to "suffer" are the exchanges. And I don't see a way to make exchanges "suffer" other than by having their suffering customers complain to them constantly that they need to update. ^ CLI has something similar where users need to set a manual payment ID transfer mode. Not sure if it's merged yet the way to make the exchanges suffer is when we ban PIDs. They either upgrade or don't use Monero. exact;y Agree with rerahr here have exchanges been provided with clear, practical, sufficient technical upgrade plans for supporting what they're doing with PIDs but with subaddrs? Both are poor options, but 1 is better than 2 by a long shot <= I wouldn't call 1. a poor option. Have you actually checked how it looks? Because it states "Payment ID" and a user has to click on the + to expand the field endogenic: yes the email when out. Blog post coming soon, but contains the same info as the email also the exhcnages' users are often using wallets that don't support subaddresses ok great as well, it should be noted that the timeline for exchanges to upgrade is September, not October when the fork is. Which wallets are that? Rehrar: I don't see option 1. causing any issues/confusion i guess it doesnt matter too much if withdrawing as a personal user the main address should suffice Because September is when the new versions will be coming out without PIDs in the UI If there's opposition to 2, 1 is fine. We can still call it deprecated which is the optics we need anyway exchange users are often just using other exchanges lol. No wallets involved. dsc_ dEBRUYNE, ok, I trust you guys here then rbrunner: i was thinking mymonero last i heard Ok pigeons: rbrunner yes receiving on subaddresses won't be supported yet sending to them has been possible though and yes as learnandlurkin says often they withdraw to other systems like exhcnages that also dont yet support subaddresses I really can't come up with any good argument for 2. right now endogenic: seems not much of an issue then. Exchanges will typically support withdrawals to both subaddresses and plain addresses (especially if we are going to force them to use subaddresses) For deposits, MyMonero works properly if the user sends to a subaddress Actually the second solution was already merged: https://github.com/monero-project/monero-gui/pull/1866 Maybe not enough eyes watching :) The important thing is to have done something to justify having a big "DEPRECATED IN APRIL" stamp on PIDs to spook exchanges in the interim This was for solution 1: https://github.com/monero-project/monero-gui/pull/1855 The Monero Community Workgroup will start making noise everywhere we can to exchanges, and everywhere else that will listen. Try to get on those garbage news sites also. So everyone knows that deprecated in April, and banned in September Hey, for solution 1, write "Payment ID (optional, deprecated)" or similar there rbrunner: noted rehrar: probably wait until the blog post, but it should only be a few days Maybe a Reddit sticky post would be useful? With the blog post If people are over freaking out about the hashrate or terabyte blockchain :) sigh Any questions for the MRL side? Is someone checking ArticMine's block size changes for weird behaviour in some cases etc ?