https://cdn.pixabay.com/photo/2016/09/23/21/08/motorcycle-1690452_1280.jpg <center><H1>Current Status</H1></center> Significant progress is being made with [hardfork 20](https://steemit.com/steemit/@steemitblog/proposing-hardfork-0-20-0-velocity), including some additional changes which will make the Steem blockchain even better. There is no official release date yet, but a release candidate is expected to be ready by the end of the year. <h2>Improving Curation Incentives</h2> <h3>Changes to 30-minute Curation Window</h3> As of now, Steem account holders (including bot accounts) are disincentivized by the Steem blockchain from voting on a post within the first 30 minutes. The earlier a vote is made within the initial 30-minute window, the less curation rewards the voting account receives. This was originally introduced to even the playing field between human curators and bots. This was successful but with the rise of more short-form content on the platform (content that can be read or viewed in less than 30 minutes), the community and the witnesses have come to a consensus that the 30-minute rule is taking curation rewards away from human voters who are actively consuming content and voting on material they like. For this reason, HF20 will reduce this window from 30 to 15 minutes. <h3>Eliminating self-voting rewards through curation</h3> While the change to 15 minutes will even the playing field against bots, it doesn’t address the advantage self-voting gives to accounts with respect to curation rewards. If authors vote for themselves right away, they get their author rewards, 100% of the curation rewards from their vote, plus a portion of the curation rewards coming from everyone who votes for the post after them. Any other curator voting at the same time as the author would get 0% of the curation rewards. This gives the author an unfair advantage over other curators because the author can earn additional curation rewards through self-voting. In order to eliminate this unfair advantage, the unused portion of the curation rewards will be returned to the rewards pool instead of being awarded to the author, thereby increasing the overall percentage of rewards that will be paid to curators. This will better serve the original mission of the curation rewards budget: to ensure that the Steem blockchain distributes rewards to the most valuable content. <h2>“Dust” vote changes</h2> <h3>Removal of vote dust threshold</h3> The "vote dust threshold" is a rule that prevents the occurrence of extremely weak votes. Currently, accounts must possess about 1 SP in order for a 100% Voting Power vote to be successfully posted to the blockchain. If a vote is placed that is below the required threshold, it will be rejected by the blockchain. This can create a bad user experience for new users, as their votes can fail for seemingly no reason. In hardfork 20, this “vote dust threshold” will be removed. After this change users with any amount of SP will be able to cast votes so long as they have sufficient bandwidth. Votes that are below the threshold will be posted to the blockchain but will have no impact on rewards. This will allow users to have a better user experience on all Steem-based applications by enabling them to vote whenever they want to (as long as they don’t exceed their generous bandwidth allocation), without adding to the computational load on the blockchain by requiring that it calculate the impact of effectively powerless votes on the rewards pool. This also mitigates an attack vector by ensuring that if a malicious actor wanted to overburden the Steem blockchain, making countless small votes would not be an effective strategy. <h3>Application of shift to all votes</h3> The switch to linear rewards in hardfork 19 has had a very positive effect on user experience. HF19 ensured that the impact of each user’s vote on the rewards pool is directly proportional to their Steem Power (i.e. their stake in the platform). Users now feel more empowered, and they can see the direct correlation between the amount of Steem Power they have and the strength of their vote. However, the switch to a linear rewards curve meant that there was less of a disincentive for casting lots of inconsequential votes (“vote spamming”). While it is important for users to be able to earn rewards whenever stakeholders (even small ones) find value in their content, it is also important to disincentivize rewarding content with respect to which no other stakeholders see value. After discussion with the witnesses, it was decided to apply the “vote dust” shift to all votes equally. Each vote that is cast will be shifted down by about 1.219 SP. This effectively establishes a “baseline” voting strength that applies to everyone, while still maintaining a linear rewards curve for votes above the baseline. This way even large Steem Power holders won’t be able to profit from casting countless inconsequential votes. <h2>Proof-of-Work account mining via softfork</h2> The changes required to add support for PoW mining for discounted accounts will be included in hardfork 20, but the actual PoW mining will be added later as a softfork on top of HF20. <h2>Removal of Power Down Restriction</h2> To prevent faucet abuse, accounts could not previously power down unless they had 10 times the account creation fee in Steem Power. Because account creation fees will now be burned with HF20, there will be less of a financial incentive to abuse faucets. After HF20, Steem account holders will have the freedom to power down their SP regardless of their account balance. <h2>Update to witness price feed format</h2> This change only affects the witnesses. A small change will be made to require the base to be SBD and the quote to be STEEM. Currently, both orders are allowed and can lead to undefined behavior in the price feed. Most witnesses are already supplying their price feeds in this format. <center><H1>Additional Details</H1></center> The full list of changes, as well as additional details not listed here, can be found in the GitHub [Steem 0.20.0](https://github.com/steemit/steem/projects/3) project. More details can also be found in the original @steemitblog proposal: [Proposing Hardfork 0.20.0 “Velocity”](https://steemit.com/steemit/@steemitblog/proposing-hardfork-0-20-0-velocity). <center><H1>Conclusion</H1></center> The changes that are coming in the Velocity hardfork are very exciting because they are establishing the foundation that will enable Steemit.com and apps built on top of Steem to onboard millions of new users while remaining economically scalable. With these changes and the additional improvements described above, the Steem platform will be better than ever! Steem on, _Team Steemit_
author | steemitblog |
---|---|
permlink | hardfork-20-velocity-development-update |
category | steem |
json_metadata | {"tags":["steem","steemit","steemdev","hf20","hardfork"],"users":["steemitblog"],"image":["https://cdn.pixabay.com/photo/2016/09/23/21/08/motorcycle-1690452_1280.jpg"],"links":["https://steemit.com/steemit/@steemitblog/proposing-hardfork-0-20-0-velocity","https://github.com/steemit/steem/projects/3"],"app":"steemit/0.1","format":"markdown"} |
created | 2017-12-20 17:29:12 |
last_update | 2017-12-20 17:29:12 |
depth | 0 |
children | 173 |
last_payout | 2017-12-27 17:29:12 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 6,789 |
author_reputation | 332,472,558,821,177 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 0.000 HBD |
percent_hbd | 10,000 |
post_id | 24,384,536 |
net_rshares | 81,769,217,306,161 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
analisa | 0 | 213,772,473,099 | 4% | ||
blocktrades | 0 | 6,903,079,382,008 | 25% | ||
wackou | 0 | 5,270,604,801,654 | 80% | ||
sandra | 0 | 13,748,772,379 | 13% | ||
ihashfury | 0 | 5,694,293,771 | 13% | ||
jason | 0 | 17,098,062,558 | 13% | ||
donkeypong | 0 | 407,267,218,242 | 4% | ||
steemitblog | 0 | 1,870,813,909,383 | 100% | ||
dan-atstarlite | 0 | 398,834,892,420 | 100% | ||
ratel | 0 | 9,607,482,430 | 40% | ||
bravenewcoin | 0 | 2,969,558,741 | 100% | ||
beervangeer | 0 | 1,202,926,144 | 100% | ||
grandpere | 0 | 16,572,992,649 | 10% | ||
knopki | 0 | 1,179,698,384 | 100% | ||
gtg | 0 | 4,349,123,604,606 | 100% | ||
stealthtrader | 0 | 0 | 100% | ||
vi1son | 0 | 70,603,143,210 | 100% | ||
ausbitbank | 0 | 1,064,408,939,092 | 11% | ||
livingfree | 0 | 126,367,056,720 | 2% | ||
vortac | 0 | 3,470,277,025,550 | 100% | ||
fulltimegeek | 0 | 119,307,036,510 | 100% | ||
thelindvall | 0 | 37,729,691,837 | 100% | ||
igster | 0 | 1,972,488,547 | 1% | ||
demotruk | 0 | 9,269,130,954 | 1% | ||
james212 | 0 | 62,142,570,454 | 100% | ||
rfresh | 0 | 5,791,588,009 | 100% | ||
alsprinting | 0 | 7,305,225,952 | 50% | ||
fabien | 0 | 475,582,520,881 | 100% | ||
dumar022 | 0 | 11,543,175,531 | 16% | ||
dez1337 | 0 | 18,379,044,182 | 25% | ||
timcliff | 0 | 465,624,469,220 | 34% | ||
velourex | 0 | 16,085,318,291 | 10% | ||
kyriacos | 0 | 63,227,659,464 | 15% | ||
gammagooblin | 0 | 25,750,888,742 | 100% | ||
nelkel | 0 | 0 | 100% | ||
steevc | 0 | 26,955,810,063 | 6% | ||
pery | 0 | 67,754,143,799 | 100% | ||
themonetaryfew | 0 | 744,009,076,492 | 100% | ||
titusfrost | 0 | 24,960,384,241 | 10% | ||
leunghakkwun | 0 | 190,758,663 | 100% | ||
rada | 0 | 375,386,489 | 100% | ||
cleateles | 0 | 1,810,890,520 | 100% | ||
bitcoinparadise | 0 | 271,834,608,034 | 100% | ||
freebornangel | 0 | 1,181,983,592 | 2% | ||
tarekadam | 0 | 693,432,195,126 | 75% | ||
triverse | 0 | 2,420,010,133 | 22% | ||
vannour | 0 | 31,346,258,765 | 100% | ||
barton26 | 0 | 5,439,165,786 | 100% | ||
blhz | 0 | 19,901,486,658 | 100% | ||
thejohalfiles | 0 | 52,539,129,752,119 | 100% | ||
jamzed | 0 | 14,187,450,338 | 100% | ||
walterjay | 0 | 185,484,277,147 | 70% | ||
raymondmendoza | 0 | 259,594,667 | 100% | ||
lifelovelifting | 0 | 1,632,429,897 | 30% | ||
da-dawn | 0 | 6,046,779,232 | 10% | ||
evildeathcore | 0 | 0 | 85% | ||
amri | 0 | 4,695,316,996 | 100% | ||
arsenal49 | 0 | 17,633,222,314 | 16% | ||
frieswiththat | 0 | 476,965,977 | 15% | ||
immetal6669 | 0 | 262,611,863 | 1% | ||
lgcct | 0 | 4,182,603,085 | 100% | ||
zappl | 0 | 0 | 100% | ||
ylgv | 0 | 2,799,601,177 | 30% | ||
indend007 | 0 | 332,866,646,500 | 70% | ||
blazin3596 | 0 | 611,120,912 | 100% | ||
weetreebonsai | 0 | 12,233,371,211 | 100% | ||
mys | 0 | 28,601,322,308 | 100% | ||
kodaxx | 0 | 15,840,316,608 | 100% | ||
azissuloh | 0 | 2,212,488,750 | 100% | ||
diogogomes | 0 | 218,446,193 | 30% | ||
wanxlol | 0 | 25,381,193,259 | 100% | ||
helo | 0 | 2,343,919,983 | 100% | ||
yguhan | 0 | 25,709,283,218 | 100% | ||
fikri | 0 | 2,807,116,436 | 100% | ||
manoloeldelbombo | 0 | 18,264,505,619 | 100% | ||
maxer27 | 0 | 16,095,641,766 | 100% | ||
hknyasar | 0 | 320,794,730 | 1% | ||
mahdiyari | 0 | 424,800,365,613 | 100% | ||
zeeree | 0 | 560,665,600 | 100% | ||
mermaid | 0 | 7,657,603,886 | 100% | ||
drakos | 0 | 18,639,831,446 | 5% | ||
davidshq | 0 | 0 | 100% | ||
samsulindra | 0 | 0 | 100% | ||
muhammadarsalan | 0 | 0 | 0% | ||
hg235 | 0 | 0 | 100% | ||
adamantine | 0 | 21,172,738,169 | 25% | ||
yanakellen | 0 | 320,532,090 | 100% | ||
jaraumoses | 0 | 4,387,935,810 | 100% | ||
jmcmeekin | 0 | 2,085,368,234 | 25% | ||
dwaeji-aizelle | 0 | 3,296,801,804 | 100% | ||
jkagub | 0 | 0 | 100% | ||
trenz | 0 | 885,051,526 | 100% | ||
amikphoto | 0 | 0 | 100% | ||
riskyalizal | 0 | 568,466,461 | 100% | ||
altsaniy | 0 | 1,216,774,358 | 100% | ||
steemreports | 0 | 30,165,118,363 | 100% | ||
yogevm | 0 | 16,553,898,228 | 100% | ||
colmanlamkh | 0 | 2,916,476,906 | 100% | ||
jesus.christ | 0 | 1,063,268,957 | 43% | ||
uberbrady | 0 | 3,297,660,473 | 100% | ||
inquiringtimes | 0 | 254,810,693,831 | 100% | ||
diskorvery | 0 | 487,357,494 | 1% | ||
jamescash | 0 | 0 | 100% | ||
bigpanda | 0 | 23,504,416,690 | 5% | ||
alcik | 0 | 6,140,055,084 | 50% | ||
iskandarpcc | 0 | 1,412,190,840 | 100% | ||
duekie | 0 | 274,407,812 | 100% | ||
design-guy | 0 | 7,948,329,577 | 100% | ||
maxiemoses-eu | 0 | 554,470,400 | 100% | ||
chieppa1 | 0 | 10,410,930,079 | 100% | ||
perthmint | 0 | 396,783,278 | 64% | ||
my451r | 0 | 2,089,933,859 | 100% | ||
nikez452 | 0 | 20,340,689,466 | 1% | ||
shweyaungmyanmar | 0 | 4,754,907,881 | 100% | ||
hato | 0 | 18,467,203,924 | 100% | ||
hayat | 0 | 0 | 100% | ||
anna-mi | 0 | 1,615,368,895 | 100% | ||
gameoutcome | 0 | 554,083,651 | 27% | ||
tonygreene113 | 0 | 103,215,361 | 1% | ||
ralif | 0 | 8,266,122,347 | 100% | ||
ankursengupta | 0 | 0 | 100% | ||
humanabstract | 0 | 1,751,074,982 | 100% | ||
zinovi | 0 | 27,567,416,432 | 100% | ||
rayken04 | 0 | 60,142,208 | 10% | ||
outwalking | 0 | 563,425,098 | 50% | ||
akeemqaz | 0 | 506,322,772 | 100% | ||
mart101 | 0 | 543,153,600 | 100% | ||
afterglow | 0 | 2,280,407,666 | 100% | ||
idlebright | 0 | 7,498,968,857 | 100% | ||
steemgogo99 | 0 | 601,809,000 | 100% | ||
steemvoterus | 0 | 580,186,800 | 100% | ||
belyrub | 0 | 606,193,648 | 100% | ||
bosteer | 0 | 582,850,055 | 100% | ||
beelyrub | 0 | 605,552,908 | 100% | ||
minowboster | 0 | 584,818,647 | 100% | ||
belyrubbank | 0 | 604,992,577 | 100% | ||
boostr | 0 | 583,660,559 | 100% | ||
bellurub | 0 | 386,378,476 | 100% | ||
minnoowboster | 0 | 602,830,410 | 100% | ||
kibls | 0 | 0 | 100% | ||
dianna1 | 0 | 1,083,013,412 | 100% | ||
freewalet | 0 | 386,339,667 | 100% | ||
mil499999 | 0 | 602,649,835 | 100% | ||
familytree | 0 | 0 | 100% | ||
dranren | 0 | 1,515,711,108 | 100% | ||
amaiman | 0 | 2,932,435,969 | 100% | ||
poloniexcom | 0 | 580,367,204 | 100% | ||
vuntul | 0 | 579,711,688 | 100% | ||
ungahnya | 0 | 580,367,003 | 100% | ||
tampiling | 0 | 579,865,850 | 100% | ||
siwahi | 0 | 579,557,421 | 100% | ||
tahaniae | 0 | 579,480,321 | 100% | ||
lumbus | 0 | 579,403,222 | 100% | ||
qulung | 0 | 579,403,222 | 100% | ||
danilongor | 0 | 579,326,114 | 100% | ||
caliwang | 0 | 579,249,012 | 100% | ||
gegilaan | 0 | 579,210,458 | 100% | ||
sarafff | 0 | 579,210,458 | 100% | ||
mdamanulla69 | 0 | 172,289,600 | 100% | ||
apanyagerang | 0 | 600,776,805 | 100% | ||
b4nt4t | 0 | 600,776,805 | 100% | ||
c4ncut | 0 | 579,249,013 | 100% | ||
d4ngk4k | 0 | 579,094,783 | 100% | ||
empret99999 | 0 | 579,056,223 | 100% | ||
fungullalu | 0 | 579,056,223 | 100% | ||
rabahwaluhkuam | 0 | 579,056,226 | 100% | ||
gambutttan | 0 | 579,056,226 | 100% | ||
h4yuk4m | 0 | 579,056,226 | 100% | ||
ib4l4mpik | 0 | 579,017,675 | 100% | ||
j4butam | 0 | 578,979,123 | 100% | ||
lengodah | 0 | 578,979,123 | 100% | ||
k4ntuttt | 0 | 578,979,123 | 100% | ||
m4mpusam | 0 | 578,979,123 | 100% | ||
jel | 0 | 1,632,440,279 | 100% | ||
daryjean | 0 | 189,590,916 | 100% | ||
haduhh | 0 | 601,336,665 | 100% | ||
barbara12 | 0 | 381,498,400 | 100% | ||
ratikkelambumu | 0 | 600,896,751 | 100% | ||
xiuxiu9 | 0 | 600,896,751 | 100% | ||
yondel | 0 | 600,896,751 | 100% | ||
otekiwak | 0 | 600,896,751 | 100% | ||
wadaukaring | 0 | 600,856,760 | 100% | ||
bangsat | 0 | 385,113,321 | 100% | ||
g1l4banar | 0 | 600,736,793 | 100% | ||
hitz99 | 0 | 600,736,793 | 100% | ||
antutlebong | 0 | 385,036,419 | 100% | ||
hamada-ch | 0 | 0 | 100% | ||
somethinfishy | 0 | 615,320,000 | 100% | ||
vispasian | 0 | 118,215,877 | 100% | ||
kevinwinehouse | 0 | 615,320,000 | 100% | ||
idikuci | 0 | 60,074,075,493 | 100% | ||
ogure | 0 | 460,350,022 | 100% | ||
ardx.kez14 | 0 | 67,703,247 | 100% | ||
poyraz | 0 | 612,278,831 | 100% | ||
sonny.dharmawan | 0 | 1,484,514,370 | 2% | ||
teamfed | 0 | 1,064,136,417 | 100% | ||
nikonmarshall | 0 | 3,395,609,628 | 100% | ||
tmdhml | 0 | 1,038,880,379 | 100% | ||
dmwh | 0 | 10,103,293,337 | 50% | ||
diini | 0 | 506,076,631 | 100% | ||
khatab505 | 0 | 1,121,320,753 | 100% | ||
cryptodox | 0 | 237,798,272 | 100% | ||
a-d | 0 | 610,208,343 | 100% | ||
justgoscha | 0 | 3,847,030,176 | 100% | ||
antbelas | 0 | 961,273,761 | 100% | ||
frank1in | 0 | 175,426,310 | 100% | ||
maovader888 | 0 | 52,302,200 | 100% | ||
fdudaie | 0 | 505,974,951 | 100% | ||
wehmoen | 0 | 2,478,261,803 | 100% | ||
yakubenko | 0 | 358,535,303 | 100% | ||
daniel-rojas | 0 | 778,831,366 | 100% | ||
kolat | 0 | 396,881,400 | 100% | ||
muchlove | 0 | 58,455,400 | 100% | ||
usmanirshad | 0 | 236,898,200 | 100% | ||
imranpase2000 | 0 | 203,240,137 | 100% | ||
slacktmusic | 0 | 893,624,638 | 100% | ||
jakeybrown | 0 | 829,764,974 | 100% | ||
grandphilippe | 0 | 1,102,484,365 | 100% | ||
cryptotortoise | 0 | 1,096,681,767 | 100% | ||
rafiqi47 | 0 | 731,146,621 | 100% | ||
itsben | 0 | 371,376,000 | 100% | ||
weird001 | 0 | 1,148,943,865 | 100% | ||
safruddin88 | 0 | 0 | 100% | ||
jiglifyy | 0 | 81,235,392 | 100% | ||
almagatuna | 0 | 116,050,450 | 100% | ||
dylansjourney | 0 | 1,119,886,835 | 100% | ||
blazinbob419 | 0 | 887,785,707 | 100% | ||
bigguyandrusty | 0 | 1,096,675,680 | 100% | ||
andaluzsteph | 0 | 812,352,346 | 100% | ||
danu-drj | 0 | 707,907,022 | 100% | ||
kromander | 0 | 1,108,280,525 | 100% | ||
akaipa | 0 | 1,119,885,273 | 100% | ||
gadol | 0 | 0 | 0% | ||
malembe | 0 | 1,160,499,115 | 100% | ||
chrisbaty | 0 | 0 | 100% | ||
ghanexs | 0 | 0 | 100% | ||
aliahmadwattoo | 0 | 0 | 100% | ||
thenigerianone | 0 | 0 | 100% | ||
sofievanrooij | 0 | 0 | 0% | ||
yusuf20 | 0 | 0 | 100% | ||
pure-heart | 0 | 0 | 100% | ||
harki | 0 | 0 | 100% | ||
iownhell | 0 | 0 | 100% | ||
fjsegura | 0 | 0 | 100% | ||
abelidrogo | 0 | 0 | 100% | ||
stanleyftf | 0 | 0 | 100% | ||
cryptocionnews | 0 | 0 | 100% | ||
ilyazkhan8082 | 0 | 0 | 100% | ||
radamimuhammad | 0 | 0 | 100% | ||
hrissm | 0 | 0 | 100% | ||
troyshein | 0 | 0 | 100% | ||
mixmatchmag | 0 | 0 | 100% | ||
zaq8710 | 0 | 0 | 100% | ||
chicapasion | 0 | 0 | 100% | ||
samlach | 0 | 0 | 100% | ||
jeftek | 0 | 0 | 100% | ||
umbraticdesigns | 0 | 0 | 100% | ||
iboy-fx | 0 | 0 | 100% | ||
purnawarman | 0 | 0 | 100% | ||
derhexer | 0 | 0 | 100% | ||
leadingmindslab | 0 | 0 | 100% |
I love the 30 minutes to 15 minutes curation window change.
author | afterglow |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171221t130700424z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-21 13:07:15 |
last_update | 2017-12-21 13:07:15 |
depth | 1 |
children | 0 |
last_payout | 2017-12-28 13:07:15 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 59 |
author_reputation | 308,361,005,596,077 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,520,350 |
net_rshares | 0 |
Can't wait these changes to come, I think they'll affect positively the plattform and incentive curation.
author | airmatti |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171222t092636005z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-22 09:26:39 |
last_update | 2017-12-22 09:26:39 |
depth | 1 |
children | 0 |
last_payout | 2017-12-29 09:26:39 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 105 |
author_reputation | 28,523,573,828,702 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,666,304 |
net_rshares | 0 |
Ok I did my reading here also reading all comments and I must say what the heck are you people talking about?
author | artbenow |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171220t175854991z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-20 17:58:54 |
last_update | 2017-12-20 17:58:54 |
depth | 1 |
children | 1 |
last_payout | 2017-12-27 17:58:54 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 109 |
author_reputation | 850,079,719,099 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,389,077 |
net_rshares | 0 |
Some of us are talking about details from the announcement, some are comment spamming ;)
author | reggaemuffin |
---|---|
permlink | re-artbenow-re-steemitblog-hardfork-20-velocity-development-update-20171220t183901492z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-20 18:39:00 |
last_update | 2017-12-20 18:39:00 |
depth | 2 |
children | 0 |
last_payout | 2017-12-27 18:39:00 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 88 |
author_reputation | 37,964,839,695,531 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,394,988 |
net_rshares | 2,788,726,081 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
vitkolesnik | 0 | 2,788,726,081 | 10% |
thank you for the power down thingy!!
author | chelinxar1 |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171221t231451975z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-21 23:14:51 |
last_update | 2017-12-21 23:14:51 |
depth | 1 |
children | 0 |
last_payout | 2017-12-28 23:14:51 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 37 |
author_reputation | 7,566,305,766 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,601,799 |
net_rshares | 0 |
## [A]ccount creation fees will now be burned with HF20 Let the burn the fire!
author | clayop |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171220t201143808z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-20 20:11:42 |
last_update | 2017-12-20 20:11:42 |
depth | 1 |
children | 2 |
last_payout | 2017-12-27 20:11:42 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 5.010 HBD |
curator_payout_value | 0.581 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 78 |
author_reputation | 270,845,899,918,618 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,407,075 |
net_rshares | 896,443,111,089 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
clayop | 0 | 298,287,523,947 | 36% | ||
stealthtrader | 0 | 12,559,907,240 | 100% | ||
lgcct | 0 | 4,262,525,437 | 100% | ||
indend007 | 0 | 466,013,305,101 | 100% | ||
wanxlol | 0 | 21,053,760,988 | 100% | ||
coffeenut | 0 | 7,411,113,145 | 20% | ||
humanabstract | 0 | 1,721,727,357 | 100% | ||
juicy-shark | 0 | 80,026,162,923 | 100% | ||
daniyal32 | 0 | 596,860,400 | 100% | ||
nikonmarshall | 0 | 3,349,723,012 | 100% | ||
jennie-luv | 0 | 1,160,501,539 | 100% |
The fire rises!
author | distantsignal |
---|---|
permlink | re-clayop-re-steemitblog-hardfork-20-velocity-development-update-20171222t171852716z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-22 17:18:51 |
last_update | 2017-12-22 17:18:51 |
depth | 2 |
children | 0 |
last_payout | 2017-12-29 17:18:51 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 15 |
author_reputation | 32,496,313,953,302 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,728,319 |
net_rshares | 0 |
RIP Account Creation Fee's!
author | reseller |
---|---|
permlink | re-clayop-re-steemitblog-hardfork-20-velocity-development-update-20171225t034230136z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-25 03:42:33 |
last_update | 2017-12-25 03:42:33 |
depth | 2 |
children | 0 |
last_payout | 2018-01-01 03:42:33 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 27 |
author_reputation | 396,642,162,962,533 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 25,108,805 |
net_rshares | 3,701,395,268 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
reseller | 0 | 3,701,395,268 | 10% |
Is there any date when we can expect HF20?
author | crypto-econom1st |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20180423t042725532z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2018-04-23 04:27:27 |
last_update | 2018-04-23 04:27:27 |
depth | 1 |
children | 0 |
last_payout | 2018-04-30 04:27:27 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 42 |
author_reputation | 4,447,971,413,472 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 51,604,319 |
net_rshares | 0 |
You forgot ONE very important thing: Reduce bandwidth! Witnesses will thank you! Because it is good to make account creation easier. It is good to have more fair rewards. It is great to discourage bots, but we already have a very busy blockchain. More bots will come, they'll create more SPAM transactions, we have to reduce bandwidth or set transaction fees AND nobody likes fees!
author | develcuy |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171220t190613448z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-20 19:06:15 |
last_update | 2017-12-20 19:06:15 |
depth | 1 |
children | 2 |
last_payout | 2017-12-27 19:06:15 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.801 HBD |
curator_payout_value | 0.113 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 381 |
author_reputation | 4,853,554,441,622 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,398,740 |
net_rshares | 146,701,426,103 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
moisesmcardona | 0 | 3,437,405,929 | 3% | ||
manosteel211 | 0 | 7,444,833,385 | 50% | ||
develcuy | 0 | 15,695,391,740 | 100% | ||
dropahead | 0 | 18,350,838,396 | 50% | ||
valth | 0 | 22,703,635,607 | 30% | ||
ana2410 | 0 | 53,467,684 | 20% | ||
indiantraveller | 0 | 729,606,348 | 5% | ||
nadieyja | 0 | 108,445,021 | 10% | ||
antoniomontilva | 0 | 400,542,363 | 100% | ||
jmourad | 0 | 89,547,624 | 20% | ||
joyita | 0 | 8,615,741,489 | 100% | ||
dailygrcstats | 0 | 222,513,115 | 5% | ||
embalsespr | 0 | 53,007,553 | 5% | ||
trailhispano | 0 | 75,957,425 | 5% | ||
mystic-natura | 0 | 126,941,303 | 20% | ||
proba1 | 0 | 306,227,871 | 50% | ||
nnnarvaez | 0 | 37,240,476,761 | 40% | ||
bebeth | 0 | 22,642,602,449 | 40% | ||
three.colours | 0 | 52,302,200 | 12% | ||
erfiguera | 0 | 55,378,800 | 20% | ||
bienvenida | 0 | 97,531,516 | 5% | ||
faiber | 0 | 66,743,038 | 20% | ||
preguntame | 0 | 51,311,819 | 5% | ||
marilia | 0 | 7,918,744,231 | 100% | ||
amigoos | 0 | 52,302,200 | 10% | ||
picj | 0 | 55,378,800 | 20% | ||
iricardoxd | 0 | 54,551,436 | 10% |
Valuable point. I would suggest reducing voting power for transactions the same way as vote.
author | bronevik |
---|---|
permlink | re-develcuy-re-steemitblog-hardfork-20-velocity-development-update-20171221t020425356z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-21 02:03:03 |
last_update | 2017-12-21 02:03:03 |
depth | 2 |
children | 0 |
last_payout | 2017-12-28 02:03:03 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 1.111 HBD |
curator_payout_value | 0.369 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 92 |
author_reputation | 12,260,156,653,305 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,445,724 |
net_rshares | 239,030,126,977 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
bronevik | 0 | 239,030,126,977 | 100% |
That's a good point! I have probably got a hundred spam transactions to my wallet of the last months, and it would be great if it was easier to prevent this.
author | valth |
---|---|
permlink | re-develcuy-re-steemitblog-hardfork-20-velocity-development-update-20171220t205423230z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-20 20:54:24 |
last_update | 2017-12-20 20:54:24 |
depth | 2 |
children | 0 |
last_payout | 2017-12-27 20:54:24 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 157 |
author_reputation | 74,218,254,347,006 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,412,086 |
net_rshares | 0 |
Nice! I love to read this :) Could you please tell me if the code cleanups and the api changes (e.g return and args objects) are already included in HF 20? By the way: As a third party / api wrapper dev I have to say thank you for the good communication .. it has been improved a lot over the last year 😍
author | dez1337 |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171221t082838595z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-21 08:28:42 |
last_update | 2017-12-21 08:28:42 |
depth | 1 |
children | 0 |
last_payout | 2017-12-28 08:28:42 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.443 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 307 |
author_reputation | 20,544,257,521,749 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,488,113 |
net_rshares | 71,518,454,537 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
dez1337 | 0 | 71,518,454,537 | 100% |
What's wrong with having a math problem or slide the puzzle piece like Binance.com in order to vote or comment? Then you could go by page views and comments.
author | dking333 |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20180323t013106315z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2018-03-23 01:31:06 |
last_update | 2018-03-23 01:31:06 |
depth | 1 |
children | 0 |
last_payout | 2018-03-30 01:31:06 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 157 |
author_reputation | 15,849,616,999 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 46,055,781 |
net_rshares | 0 |
I did not understand what would happen with voting for myself.
author | dlina-v-metrah |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171220t174425096z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-20 17:44:51 |
last_update | 2017-12-20 17:44:51 |
depth | 1 |
children | 2 |
last_payout | 2017-12-27 17:44:51 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 62 |
author_reputation | 4,193,087,735,412 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,386,888 |
net_rshares | 0 |
author | bronevik |
---|---|
permlink | re-dlina-v-metrah-re-steemitblog-hardfork-20-velocity-development-update-20171221t023325598z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-21 02:32:03 |
last_update | 2017-12-21 02:32:03 |
depth | 2 |
children | 0 |
last_payout | 2017-12-28 02:32:03 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.142 HBD |
curator_payout_value | 0.003 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 19 |
author_reputation | 12,260,156,653,305 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,449,040 |
net_rshares | 23,827,425,098 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
blow | 0 | 5,186,880,345 | 100% | ||
bronevik | 0 | 18,640,544,753 | 11% |
Your share of the curation reward get added back to the reward pool if you vote within the first 15 minutes on your posts. Basically **wait 15 minutes to upvote yourself for maximum reward**.
author | valth |
---|---|
permlink | re-dlina-v-metrah-re-steemitblog-hardfork-20-velocity-development-update-20171220t210918573z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-20 21:09:21 |
last_update | 2017-12-20 21:09:21 |
depth | 2 |
children | 0 |
last_payout | 2017-12-27 21:09:21 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 191 |
author_reputation | 74,218,254,347,006 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,413,843 |
net_rshares | 0 |
Great work
author | ebosetale |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171224t224859493z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-24 22:49:06 |
last_update | 2017-12-24 22:49:06 |
depth | 1 |
children | 0 |
last_payout | 2017-12-31 22:49:06 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 10 |
author_reputation | 11,675,193 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 25,085,760 |
net_rshares | 0 |
hmm nice positive updates
author | everything-4you |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171220t190821725z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-20 19:08:24 |
last_update | 2017-12-20 19:08:24 |
depth | 1 |
children | 0 |
last_payout | 2017-12-27 19:08:24 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 25 |
author_reputation | 1,817,224,342,634 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,399,012 |
net_rshares | 951,616,223 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
everything-4you | 0 | 951,616,223 | 100% |
good changing i appreciate it https://media1.tenor.com/images/963a77735e9645c8bcf3d9d6cbca6822/tenor.gif?itemid=9541060
author | everything-4you |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171220t211014144z |
category | steem |
json_metadata | {"tags":["steem"],"image":["https://media1.tenor.com/images/963a77735e9645c8bcf3d9d6cbca6822/tenor.gif?itemid=9541060"],"app":"steemit/0.1"} |
created | 2017-12-20 21:10:15 |
last_update | 2017-12-20 21:10:15 |
depth | 1 |
children | 0 |
last_payout | 2017-12-27 21:10:15 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 120 |
author_reputation | 1,817,224,342,634 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,413,958 |
net_rshares | 760,132,471 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
everything-4you | 0 | 760,132,471 | 100% |
his beautiful postings, stop by my account and upvote him
author | fahry |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171220t180140658z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-20 18:01:45 |
last_update | 2017-12-20 18:01:45 |
depth | 1 |
children | 0 |
last_payout | 2017-12-27 18:01:45 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 57 |
author_reputation | 201,277,499,272 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,389,511 |
net_rshares | 0 |
Here is by far my favorite part of this ( or any other announcement): ### "establishing the foundation that will enable Steemit.com and apps built on top of Steem to onboard millions of new users" Yes please.
author | hanshotfirst |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171220t180236940z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-20 18:02:36 |
last_update | 2017-12-20 18:02:36 |
depth | 1 |
children | 0 |
last_payout | 2017-12-27 18:02:36 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.502 HBD |
curator_payout_value | 0.162 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 210 |
author_reputation | 688,565,082,268,258 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,389,628 |
net_rshares | 106,712,949,398 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
abh12345 | 0 | 22,781,952,061 | 3% | ||
destinysaid | 0 | 83,930,997,337 | 30% |
This is a very good step in the right direction. Protecting both the author and the curator. I'm especially fond of the 30-minute timeframe reduction. Very excited for these changes to take effect. Very excited!
author | iamnotageek |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171220t195634025z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-20 19:56:36 |
last_update | 2017-12-20 19:56:36 |
depth | 1 |
children | 0 |
last_payout | 2017-12-27 19:56:36 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 213 |
author_reputation | 8,034,737,956,380 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,405,259 |
net_rshares | 0 |
seems to be making steem fairer
author | immetal6669 |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171226t185753281z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-26 18:57:39 |
last_update | 2017-12-26 18:57:39 |
depth | 1 |
children | 0 |
last_payout | 2018-01-02 18:57:39 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.100 HBD |
curator_payout_value | 0.032 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 31 |
author_reputation | 1,124,005,066,656 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 25,386,125 |
net_rshares | 23,022,101,458 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
immetal6669 | 0 | 23,022,101,458 | 100% |
when is hf20 planned to be? any eta?
author | investwarrior |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171222t101420148z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-22 10:13:57 |
last_update | 2017-12-22 10:13:57 |
depth | 1 |
children | 0 |
last_payout | 2017-12-29 10:13:57 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 36 |
author_reputation | 3,530,100,550,242 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,671,709 |
net_rshares | 0 |
<a href="https://imgflip.com/i/21f95h"><img src="https://i.imgflip.com/21f95h.jpg" title="made at imgflip.com"/></a>
author | jaraumoses |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171220t174910171z |
category | steem |
json_metadata | {"tags":["steem"],"image":["https://i.imgflip.com/21f95h.jpg"],"links":["https://imgflip.com/i/21f95h"],"app":"steemit/0.1"} |
created | 2017-12-20 17:49:18 |
last_update | 2017-12-20 17:49:18 |
depth | 1 |
children | 0 |
last_payout | 2017-12-27 17:49:18 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 116 |
author_reputation | 85,212,359,587,812 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,387,547 |
net_rshares | 0 |
There should be limit on earnings also....No post should get more than 500 SBD.... 500 * 15 = 7500 $ is more than sufficient for single post... Thankyou... 
author | kartiksingh |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171220t182856039z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1","image":["https://media.giphy.com/media/s4UinMCH5cHdu/giphy.gif"]} |
created | 2017-12-20 18:28:57 |
last_update | 2017-12-20 18:31:39 |
depth | 1 |
children | 1 |
last_payout | 2017-12-27 18:28:57 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.102 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 217 |
author_reputation | 30,641,753,110,789 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,393,531 |
net_rshares | 16,601,541,482 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
kartiksingh | 0 | 16,601,541,482 | 100% |
I think the potential challenge here is, as others build platforms off of Steem, and if you want to attract much more high profile creators, some of them are likely making more than $7500 on some pieces of content (thinking about YouTubers specifically). As such, a hard cap makes the potential for earnings less attractive.
author | gyrosean |
---|---|
permlink | re-kartiksingh-re-steemitblog-hardfork-20-velocity-development-update-20171220t194258496z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-20 19:42:57 |
last_update | 2017-12-20 19:42:57 |
depth | 2 |
children | 0 |
last_payout | 2017-12-27 19:42:57 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 324 |
author_reputation | 5,083,540,037,277 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,403,485 |
net_rshares | 0 |
> This was successful but with the rise of more short-form content on the platform (content that can be read or viewed in less than 30 minutes), the community and the witnesses have come to a consensus that the 30-minute rule is taking curation rewards away from human voters who are actively consuming content and voting on material they like. For this reason, HF20 will reduce this window from 30 to 15 minutes. I find it difficult to imagine that no one but me sees the obvious problem with this solution. What human being spends 24 hours a day sitting on Steemit waiting for content? Does not the usual use case suggest that people have lives that they go about, and occasionally engage with one to two hour sessions – if that – of using the platform actively? Doesn't that suggest that a shorter curation reward window actually rewards bots far more than human beings, who are much more likely to discover the existence of the post or comment well outside of a 30 minute window. Possibly, given the amount of time it takes to recharge Voting Power, on the order of a couple of days between major sessions of engagement with the platform. This rule seems specifically and explicitly designed to privilege bot monitoring of feed streams much more than human engagement. Even for short-form content, the discovery time is going to be well beyond 15 minutes. I'm not even suggesting that this idea is wrongheaded. It's just wrong. It's exactly the wrong direction for solving the problem you say it's supposed to solve. If you want to reduce the advantage that bot voting has over humans, reduce the advantages that bots have over humans. Make the curation reward window a day long, drop the decaying payoff aspect, and simply treat all upvotes within the window completely equally. Then humans and human curation actually has a chance to find this content and vote it up and aren't penalized for not being a bot with nothing else to do. HF 20 is going to increase the number of bots that people use to get maximum curation awards. You get what you reward, and you are rewarding and automated process which merely looks for new updates on feeds that are likely to be popular, tries to wait for the optimum number of minutes, and then puts in a vote. It has nothing to do with the content. This effectively makes the content mean even less in the context of human interaction. Congratulations. That's quite impressive. > This will better serve the original mission of the curation rewards budget: to ensure that the Steem blockchain distributes rewards to the most valuable content. Wouldn't it be much simpler to simply remove self-voting from the system and maintain the rest of the architecture as is? That would immediately and completely reduce the author's rewards from any curational activity without pouring any funds back into the top of the hopper – in theory rewarding people who weren't even involved in either creation or curation of the piece in any way. In fact, that would suggest that the greatest stakeholders have an even higher motivation to choke off rewards to people they don't like rather than reward content that they do like. All of that money goes back into the hopper and has a much greater statistical likelihood of landing on their head, after all. I reiterate, you get what you reward. Stop rewarding self voting by making it impossible and you'll still get curation and creation. Simply "redistribute" the authors' cut that you think they don't deserve and you'll get less authors and more people interested in "redistributing" those funds largely back to themselves. > In hardfork 20, this “vote dust threshold” will be removed. After this change users with any amount of SP will be able to cast votes so long as they have sufficient bandwidth. Votes that are below the threshold will be posted to the blockchain but will have no impact on rewards. Will accounts which actually possess SP be able to lodge effectively zero SP votes on content? This might actually provide us an opportunity to differentiate content which "more people should see" (social upvote) from "I think this author deserves some money for what they're doing." And yes, those are different ideas and different things which cannot at this point be signaled to the system differently. For a social network, it's amazingly non-social. Allowing that finer grained expression of intent will actually be a positive help. > ... it is also important to disincentivize rewarding content with respect to which no other stakeholders see value. Why? This is a contention without any support. Why would it be important to the platform to dis-incentivize voting up content that you legitimately see as valuable, no matter what other people think of its value? After all, the underlying assumption is that if I think it's valuable than somebody out there is also likely to think it's valuable and I should reward it. The alternative is in many respects what we see now: chasing the Dragon. Everyone is looking to jump on board the next big viral hit and playing the numbers to do so because the actual content doesn't matter, rather than simply seeking out what they find to be good and valuable and rewarding it. Likewise, on the creator side, chasing the Dragon ends up with a vast number of crappy, minimal effort, minimal investment posts about cryptocoin and cheerleading for STEEM – which are rewarded because everyone sees that they are valuable in the sense of can easily acquire tons of upvotes, and you get the social network equivalent of incest. That surely can't be exactly what you want. And yet – that's what you reward. > The changes required to add support for PoW mining for discounted accounts will be included in hardfork 20, but the actual PoW mining will be added later as a softfork on top of HF20. Isn't this really just a backdoor way to get proof of work mining into the STEEM blockchain? With the removal of the powerdown restriction, even with the account creation fee getting burned rather than turning into SP for a new account, this just looks like one more way to get swarms of vote dust bots to leverage hovering around the SP baseline. Worse, the people that can afford to run bots in numbers are exactly the kind of people who can afford to run proof of work mining systems in order to create bot accounts in numbers at an even steeper discount. Along with the changes to the payout timing window, this is one more place that more bot interaction is going to become ever more frequent rather than diminish. I admit, I am not feeling particularly sanguine about these changes. From a user perspective, particularly one who is interested in the social network aspects of the system, these look to dis-incentivize interaction with the blockchain as a person, dis-incentivize being a creator even over what the situation is now, and open the door to even more bots at every turn. It's as though the expected use case was never for people to be using the system at all. I feel like that's kind of a problem. I may be the only one, but that's where I'm at'.
author | lextenebris |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171220t192739488z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-20 19:27:42 |
last_update | 2017-12-20 19:33:36 |
depth | 1 |
children | 41 |
last_payout | 2017-12-27 19:27:42 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 74.780 HBD |
curator_payout_value | 24.913 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 7,105 |
author_reputation | 19,924,980,499,611 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,401,545 |
net_rshares | 15,964,734,453,408 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
sethlinson | 0 | 0 | 21% | ||
wandereronwheels | 0 | 0 | 0% | ||
seekerjuice | 0 | 0 | 100% | ||
crypto2crypto | 0 | 0 | 1% | ||
valued-customer | 0 | 25,837,427,149 | 100% | ||
uberbrady | 0 | 3,279,541,459 | 100% | ||
binkley | 0 | 0 | 100% | ||
bronevik | 0 | 125,823,677,085 | 73% | ||
ankursengupta | 0 | 0 | 100% | ||
eirsanctum | 0 | 0 | 100% | ||
peaceandlove | 0 | 15,808,984,261,964 | 100% | ||
fortunee | 0 | 0 | 100% | ||
elseleth | 0 | 0 | 100% | ||
gillianpearce | 0 | 0 | 100% | ||
greycrasan | 0 | 809,545,751 | 100% | ||
hrissm | 0 | 0 | 100% | ||
roscoeh | 0 | 0 | 100% | ||
leadingmindslab | 0 | 0 | 100% |
at the end of day we have to ask ourselves do we need curation reward that much? With any set of rules imaginable it will be bots playground.
author | bronevik |
---|---|
permlink | re-lextenebris-re-steemitblog-hardfork-20-velocity-development-update-20171221t022414420z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-21 02:22:54 |
last_update | 2017-12-21 02:22:54 |
depth | 2 |
children | 6 |
last_payout | 2017-12-28 02:22:54 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 1.047 HBD |
curator_payout_value | 0.301 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 141 |
author_reputation | 12,260,156,653,305 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,447,982 |
net_rshares | 217,608,984,055 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
valued-customer | 0 | 6,178,515,188 | 25% | ||
bronevik | 0 | 208,279,424,647 | 100% | ||
lextenebris | 0 | 3,151,044,220 | 22% |
I believe in observing the ecology to determine what's going on in it and what those who participate in it want and need. Given that the vast bulk of the people operating on the blockchain are engaged in curation manipulation in order to acquire reward, then I think it's safe to say – judging by the rules that Steem, Inc. have laid forth, people really do need curational awards that much. They want them. They want to engage with them. Just not personally. They have no interest in actually playing the curation minigame themselves. It's far more rewarding to build bots who engage in playing the curation minigame algorithmically. You get what you reward. I cannot imagine a number of sets of rules which will not advantage automation significantly, but all of them ultimately hinge on making a change in basic assumptions about what STEEM means in the blockchain. At this point, the basic commodity itself exists purely as an authoritarian, top-down assessment of your value to either create or successfully bet on pseudo-viral content. Not content which is good or reportable to a community, but content which other people will judge to be sufficiently viral. And that's really all it means. If people like myself who are creators but who don't particularly make things which are likely to be runaway popular get rewarded, that's a pleasant accident. It means that some people probably lost their bet on me and my work. Worse, it means that if they did vote my stuff up with the intention of me being rewarded for providing them something that they liked – the mechanics of the game say that they're playing it wrong. That's not how to get maximum reward out of the system. From my perspective, that's very sad. Maybe I spend a lot more time thinking about how to create sets of rules that people want to play with, but it certainly not incomprehensible to me that a set of mechanics could be put together which incentivizes an individual engaging with the platform in ways that rewards them with things other than bigger numbers that they want. To do that, it takes an effort to understand what else they might want. The current population of Steemit? Most of them just want bigger numbers. And that's all. It's no great mystery. It is quite sad.
author | lextenebris |
---|---|
permlink | re-bronevik-re-lextenebris-re-steemitblog-hardfork-20-velocity-development-update-20171221t023040844z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-21 02:30:39 |
last_update | 2017-12-21 02:30:39 |
depth | 3 |
children | 0 |
last_payout | 2017-12-28 02:30:39 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 2,265 |
author_reputation | 19,924,980,499,611 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,448,855 |
net_rshares | 0 |
This is why I have proposed eliminating curation rewards altogether. I have also proposed delinking VP from SP, and instead weighting VP with reputation that is actual community vetting. It isn't stake-weighting that draws people to Steemit, but rewards. Stake-weighting was intended to incentivize investors to use SP to direct content development, but instead it has merely become a vector for financial manipulation. Coupled with a mechanism that precludes bots, Steemit would be truly a social media platform - but investors would be offered only the incentive of capital gains by which to profit from their stake. Those with the stake prefer the immediate returns gamification of rewards provide, and content be damned.
author | valued-customer |
---|---|
permlink | re-bronevik-re-lextenebris-re-steemitblog-hardfork-20-velocity-development-update-20171221t081105481z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-21 08:11:21 |
last_update | 2017-12-21 08:11:21 |
depth | 3 |
children | 4 |
last_payout | 2017-12-28 08:11:21 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.018 HBD |
curator_payout_value | 0.003 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 729 |
author_reputation | 356,453,873,649,652 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,486,288 |
net_rshares | 4,165,588,492 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
bronevik | 0 | 4,165,588,492 | 2% |
I just have to reply with: It is not that easy. You have great ideas and I agree with you on them. But. Let me tell you about the issues with them: > Make the curation reward window a day long, drop the decaying payoff aspect, and simply treat all upvotes within the window completely equally. Then humans and human curation actually has a chance to find this content and vote it up and aren't penalized for not being a bot with nothing else to do. The 30 minutes window was added to make it harder for bots. Before that bots would vote at minute 0 on popular authors and claim all curation rewards. With your solutions, there is no linear decay, so minute 0 votes are back again. You can solve that by ignoring the order of upvotes. And since all are treated equaly, the first day is not curating, but getting a piece of the pie, you will have $1000 trending posts that are a few hours old and where everyone wants to upvote them as they give good curation. These changes will either reward bots more, or add to the bandwagon effect that curation wants to prevent. > Stop rewarding self voting by making it impossible and you'll still get curation and creation. You know that if you restrict self votes hard enough, we will just have two accounts per user? one with the SP and one with the content. > Isn't this really just a backdoor way to get proof of work mining into the STEEM blockchain? No it is just a way to allow is to make creating accounts costly without having to pay a lot of steem. Means that steemit can create accounts for free without having to validate people on their uniqueness as hard as they are not giving out that much free money. And the dust threshold exactly disincentivises having a bot army, as there is now a flat cost with each vote. I think you have read that completely the wrong way. Check the link to the HF20 announcement, that explains how the mining is working and what it's goal is. > Along with the changes to the payout timing window, this is one more place that more bot interaction is going to become ever more frequent rather than diminish. I don't see it. For me as someone who develops bots, these changes give me a hard time. They don't make things easier for me. Your suggestions would. > I admit, I am not feeling particularly sanguine about these changes. From a user perspective, particularly one who is interested in the social network aspects of the system, these look to dis-incentivize interaction with the blockchain as a person, dis-incentivize being a creator even over what the situation is now, and open the door to even more bots at every turn. Well let me say this: Steem is what we make of it. And we are humans, the ones who are having a lot of power are humans too. And I encourage you to make a post about changes you want to have, make it an utopian contribution if you want. Think a long time about all the ways users can abuse them and make them air tight. And then send me your link. I will upvote it first minute and resteem it, giving you all my curation and whatnot ;) (on the condition that it is good). I am a social human being and I value interaction. No blockchain system can prevent me from doing that and I need no motivation for it. The blockchain rules are for a stable system first, for incentives second. *upvoted for visibility* PS: Find me on discord or steemit.chat if you want to have a discussion without posting to your audience :)
author | reggaemuffin |
---|---|
permlink | re-lextenebris-re-steemitblog-hardfork-20-velocity-development-update-20171221t062650337z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-21 06:26:48 |
last_update | 2017-12-21 06:28:45 |
depth | 2 |
children | 17 |
last_payout | 2017-12-28 06:26:48 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 5.942 HBD |
curator_payout_value | 1.115 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 3,439 |
author_reputation | 37,964,839,695,531 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,474,841 |
net_rshares | 1,135,557,869,906 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
andrarchy | 0 | 912,635,824,607 | 34% | ||
arcange | 0 | 40,868,136,119 | 10% | ||
raphaelle | 0 | 5,701,633,109 | 10% | ||
miketr | 0 | 2,926,550,839 | 13% | ||
sethlinson | 0 | 0 | 21% | ||
mattclarke | 0 | 33,391,131,463 | 22% | ||
raja | 0 | 11,393,176,554 | 43% | ||
reggaemuffin | 0 | 105,164,054,972 | 1% | ||
plumey | 0 | 4,830,954,342 | 20% | ||
sumayia | 0 | 2,858,812,907 | 25% | ||
uberbrady | 0 | 3,623,843,722 | 100% | ||
cryptocoiners | 0 | 6,846,274,807 | 57% | ||
agmontpetit | 0 | 0 | 100% | ||
bonggita | 0 | 2,105,413,303 | 100% | ||
nikonmarshall | 0 | 3,212,063,162 | 100% | ||
minnowboosted | 0 | 0 | -100% |
Incredibly informative and spot on. Glad to hear your thoughts on the bot issue as a bot creator. Thanks so much for this amazingly well thought out response.
author | andrarchy |
---|---|
permlink | re-reggaemuffin-re-lextenebris-re-steemitblog-hardfork-20-velocity-development-update-20171222t170923249z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-22 17:09:21 |
last_update | 2017-12-22 17:09:21 |
depth | 3 |
children | 0 |
last_payout | 2017-12-29 17:09:21 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 158 |
author_reputation | 230,168,201,522,782 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,726,924 |
net_rshares | 0 |
<blockquote> You know that if you restrict self votes hard enough, we will just have two accounts per user? one with the SP and one with the content. </blockquote> <p> You could restrict them by implementing diminishing returns: </p> <p> I think that ... </p> <ul> <li> ... <a href="https://steemit.com/steemit/@jaki01/ideas-for-more-justice-on-steemit-ideen-fuer-mehr-gerechtigkeit-auf-steemit">diminishing returns</a> would make it less attractive to upvote oneself or certain other accounts again and again. </li> <li> ... the restriction to four full paid posts per day (like it still was some hard forks ago) was very reasonable. </li> <li> ... a <a href="https://en.wikipedia.org/wiki/Sigmoid_function">sigmoid</a> reward curve would be interesting as it makes self-voting less attractive (it starts flat), but also prevents extreme rewards for single posts (as it ends flat as well). </li> </ul> <p> Further suggestions very appreciated ... </p>
author | jaki01 |
---|---|
permlink | re-reggaemuffin-re-lextenebris-re-steemitblog-hardfork-20-velocity-development-update-20171222t031155536z |
category | steem |
json_metadata | {"tags":["steem"],"links":["https://steemit.com/steemit/@jaki01/ideas-for-more-justice-on-steemit-ideen-fuer-mehr-gerechtigkeit-auf-steemit","https://en.wikipedia.org/wiki/Sigmoid_function"],"app":"steemit/0.1"} |
created | 2017-12-22 03:11:57 |
last_update | 2017-12-22 03:11:57 |
depth | 3 |
children | 0 |
last_payout | 2017-12-29 03:11:57 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 4.478 HBD |
curator_payout_value | 1.295 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 952 |
author_reputation | 537,416,167,506,424 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,626,344 |
net_rshares | 938,678,433,791 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
kobold-djawa | 0 | 151,849,004,831 | 100% | ||
davidorcamuriel | 0 | 778,757,599,779 | 50% | ||
flurgx | 0 | 0 | 12% | ||
endracsho | 0 | 8,071,829,181 | 100% | ||
eirsanctum | 0 | 0 | 100% | ||
hrissm | 0 | 0 | 100% |
> I just have to reply with: It is not that easy. The problem is that it is exactly that easy. It just requires the will to do something that works for goals that are expressed. If anyone of those three points is not attained, then something else gets done. Something else is getting done. Which leaves the rest of us to wonder which of those three points has been ill expressed. > The 30 minutes window was added to make it harder for bots. And it failed. Spectacularly. Not just a little bit, not just kind of – it failed to the point where no there is an entire complex ecology of multiple interacting bot swarms, some of them enacting proxy wars between whales. > With your solutions, there is no linear decay, so minute 0 votes are back again. You can solve that by ignoring the order of upvotes. And since all are treated equaly, the first day is not curating, but getting a piece of the pie, you will have $1000 trending posts that are a few hours old and where everyone wants to upvote them as they give good curation. Since HF 20 seems to be all about the collection of dust from low SP accounts, it doesn't really matter if minute zero votes were to come back or not. In fact, you'll notice that I specified that under my plan, all votes – no matter where they went into the cycle – would be processed in exactly the same way. Which is effectively ignoring the order of the upvotes, yes. The bandwagon effect already exists, it's just that to determine what the most likely bandwagon at any given time is requires a computer to calculate every decision at every point. Remove the advantage of the computer doing so and humans will do so more often. Of course, to really fix that particular curation problem, the total payout for a given account will probably need to be put on a pseudo-logarithmic scale, which very well could reward minnows and plankton fairly aggressively at the beginning, and every one fairly little as they add on more. Specific calibration of that level would require some experimentation, but at least it would be grounded in the experience on the ground. (Note that I have no solution for either Trending or Hot, because both of those trade on the assumption of more money from anyone and more upvotes from anyone are completely as equal as anything else, that is the top-down authoritarian view of value. One of the first things I did would be to rip both of those out and replace them with a system which at least makes a first effort at producing content which is specific to the things that you have voted up. I'm not threatened by $1000 posts who got there in an hour. That's fine with me. I'm troubled by the fact that curation is largely wasted effort if you care about the content. The content has no impact on how well or how at all curation will proceed. > You know that if you restrict self votes hard enough, we will just have two accounts per user? one with the SP and one with the content. Oh I do, and I'm perfectly aware that such a choice would be to simply delay the introduction of that player into the community which feels they need to have two accounts, one with the SP, and one with the content. But since that doesn't actually change the way things are now in any meaningful way, I'm willing to take the wash in exchange for making such arrangements easier to find. From the perspective of the new user, all you've done is to point out that they will have to buy a second account in order to compete with their basic competitors in the space – but that not for quite a while until they learn more about the mechanics of the system. > No it is just a way to allow is to make creating accounts costly without having to pay a lot of steem. Means that steemit can create accounts for free without having to validate people on their uniqueness as hard as they are not giving out that much free money. And the dust threshold exactly disincentivises having a bot army, as there is now a flat cost with each vote. I think you have read that completely the wrong way. Check the link to the HF20 announcement, that explains how the mining is working and what it's goal is. A discount create an account that I don't have to pay SP for is a lot more important than giving out free money. You have decided that by trashing the requirement that you do a basic check that someone is a unique entity, so everything is cool and ready to go. Except, of course, that you can then turn around and load that account up with SP (delegated but less) and your choice of bot engines – and you're ready to go. The problem for their approaches to dust is that they're trying to have their cake and eat it too. You can't simultaneously argue that accounts walking around, only able to emit dust which will be an advantage for newcomers and that it will not simultaneously be an advantage for new bots. Both of them are equal in use to an account who can vote with dust. But the bot can do so more frequently, more efficiently, and with better coordination with others. Advantage, bot. > I don't see it. For me as someone who develops bots, these changes give me a hard time. They don't make things easier for me. Your suggestions would. With a narrower field of time to deal with, the content only has to be up on the server for that minimum amount of time. Within it, bots will compete not to vote it up within the first 7 1/2 minutes, and will truly compete for the ability to file their particular vote sometime within eight minutes or so. Were it up to my design, I would have some random variation in bot design, just to see how much could drift before price stability reasserted itself. It won't be hard to figure out what the optimum bid weight is, and if I'm smart enough to pay attention to metadata about potential targets, I can get more specific yet > Well let me say this: Steem is what we make of it. And we are humans, the ones who are having a lot of power are humans too. And I encourage you to make a post about changes you want to have, make it an utopian contribution if you want. Think a long time about all the ways users can abuse them and make them air tight. Why does this keep falling on me? I have no interest in designing either a front end or a modification to the STEEM blockchain that would make it run better and more effectively. I've learned a few useful things in my life, amongst which is went to look at a system and realize it is too far gone for the kind of changes that it will take to make it run well, or at least to run to the specifications set out in the documentation. I will remind you that "stable system first," has but one outcome: "a system that no one uses." In on you system is perfectly stable, nothing comes along and disturbs its sweet interlude, no equilibrium is thrown free by accident or intent. If you are reaching for a stable system first, you will always find a system in which actually doing things is dis-incentivized – and such do we see. I'm not sure what point any further conversation would have. At least not until someone bothers to actually address the weaknesses that I point out and give me a good reason why those aren't weaknesses that doesn't boil down to "no, that's part of the plan." Because if they are all part of the plan – it's a shitty plan.
author | lextenebris |
---|---|
permlink | re-reggaemuffin-re-lextenebris-re-steemitblog-hardfork-20-velocity-development-update-20171221t074028050z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-21 07:40:27 |
last_update | 2017-12-21 07:40:27 |
depth | 3 |
children | 11 |
last_payout | 2017-12-28 07:40:27 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 7,284 |
author_reputation | 19,924,980,499,611 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,482,894 |
net_rshares | 0 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
binkley | 0 | 0 | 100% | ||
hrj | 0 | 0 | 100% | ||
hrissm | 0 | 0 | 100% | ||
leadingmindslab | 0 | 0 | 100% |
@reggaemuffin and @lextenebris both valid arguments, how about looking at what other platforms do to negate the use of bots such as this. One example is by capping the number of votes you can make in a specific amount of time and then showing a message saying you have made too many - after that amount has been hit multiple times there needs to be a penalty or consequence in place, for other platforms it is a temporary ban on the platform however here on Steemit you have the unique *opportunity* to provide actual fines and penalties for bot like behaviour. If you penalised or fined the bot for doing the wrong thing then you burn the fine then everyone would be better off. *Just my 2steem worth.* I think you guys are doing a great job and I see so much potential in this platform. Keep it up!
author | nikonmarshall |
---|---|
permlink | re-reggaemuffin-re-lextenebris-re-steemitblog-hardfork-20-velocity-development-update-20171221t122426372z |
category | steem |
json_metadata | {"tags":["steem"],"users":["reggaemuffin","lextenebris"],"app":"steemit/0.1"} |
created | 2017-12-21 12:24:27 |
last_update | 2017-12-21 12:24:27 |
depth | 3 |
children | 2 |
last_payout | 2017-12-28 12:24:27 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 801 |
author_reputation | 1,767,086,451,496 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,515,060 |
net_rshares | 0 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
hrissm | 0 | 0 | 100% |
I think you've got some decent objections. Maybe you should write it up as a post on its own? I think bots are a fact of life. Perhaps so much so that they ought to just be built-in to the system and integrated. No matter what algorithm you can come up with, someone will find a way to game it. The only way to win is not to play. The way bots work is that they auto-upvote posts after 'x' delay from authors x, y, and z. (There may be other ways, but those are the ones I know about). What if you just say "the people I follow automatically get upvoted?" I dunno, maybe that makes the world worse. The thing that worries me is that the number of ways to maliciously game curation awards is high, and the number of ways to do it relatively trivially is still pretty high. I don't know the solutions for that, but you've definitely started me thinking.
author | uberbrady |
---|---|
permlink | re-lextenebris-re-steemitblog-hardfork-20-velocity-development-update-20171220t224308909z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-20 22:43:09 |
last_update | 2017-12-20 22:43:09 |
depth | 2 |
children | 6 |
last_payout | 2017-12-27 22:43:09 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.532 HBD |
curator_payout_value | 0.133 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 855 |
author_reputation | 422,121,906,316 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,424,620 |
net_rshares | 107,239,068,797 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
pharesim | 0 | 98,642,527,945 | 0.02% | ||
whatsup | 0 | 2,220,312,214 | 1% | ||
uberbrady | 0 | 3,225,184,418 | 100% | ||
lextenebris | 0 | 3,151,044,220 | 22% |
> I think you've got some decent objections. Maybe you should write it up as a post on its own? You know, every time I do that, it feels like I am deliberately pandering to an obvious audience – one that isn't really my own or the one I want to build. I don't want to write about STEEM all the time. I know that makes me a weirdo around here, and I've definitely already written several articles about STEEM in my feed, but why would I want to make the people who follow me for talk about role-playing games and video games (and 3D printing, let's not forget that one) listen to me ramble about my objections to the design choices in HF 20? I really mean that as a question, notably. Yes, it would probably be worth a few bucks from some of the people who aren't on board the hype train, but is that the audience I should be courting? Is that how I should be thinking about my audience? (That gets into a lot more complicated questions about the platform as a whole, and probably questions that need to be brought up. But probably not by me.) > I think bots are a fact of life. Perhaps so much so that they ought to just be built-in to the system and integrated. No matter what algorithm you can come up with, someone will find a way to game it. For extra irony, I don't even actually mind that bots exist. All systems which involve repetitive action profit by the addition of automation. Automation is inevitable – and it's probably a good thing. I come from the world of game design, both videogame and tabletop. When we see players going out of their way to avoid engaging with a set of mechanics that is part of our game, that's an indicator of a problem. Mechanically, the upvote system and how it feeds into the user experience is what is giving rise to a desire for automation. I've had a desire for automation. Not for a vote bot, per se, in the current sense of the word – but in a bot that I could say "I'd like to vote for this" and it waits until the best, optimal time to vote for that content that I want to reward appropriately to my ability while getting the maximum result for myself. If, in the process of doing that, it could optimally decide what the best voting percentages so that I can continue to vote for things that I like in the next day without being forced to take a day off in order to have enough power to do anything useful – that would be nice, too. Where I'm from, that's a big flag to me as a designer that the mechanic that I'm avoiding is simply not fun. It's not good to engage with. It's not rewarding. It's a mini game that detracts from the goals of the platform. For me, that would be a huge signal that I need to probably cut this mechanic from the game altogether, or change it significantly so that it is worthwhile to engage with. It's very much like bots in an MMO. When you see them appearing and beginning to dominate a niche in the game, you need to look at that niche. Look at Steemit as a vast MMO – in fact, look at the entire STEEM blockchain as a vast MMO, and then look at the behavior of players on the blockchain. Figure out what they don't want to engage with. Fix that. > What if you just say "the people I follow automatically get upvoted?" There are, in fact, several bots right now on the blockchain that do exactly that. They automatically vote for anyone that you follow (adjusted by a percentage, obviously enough). There are also follow bots that monitor a given account and upvote anything that they upvote – and they may be either automated or biological. In all of these cases? It doesn't matter what the content is. The content is not judged even by an automated process to see if it's something that vote should go for – instead, the vote is made based on meta-information which has nothing to do with the content. If, as a game designer, the idea is to get the most rewards going to the best content, where "best" is content that people actually read and like – that these bots are not only available but quite prevalent is a failure signal. I don't know of any other way to put it. > The thing that worries me is that the number of ways to maliciously game curation awards is high, and the number of ways to do it relatively trivially is still pretty high. > > I don't know the solutions for that, but you've definitely started me thinking. Again, as a game designer, the obvious place to start (and mechanics are no trivial matter, you never get it right the first place) would be to at least make automated interaction with mechanic no more advantageous than human interaction with the mechanic. What's the advantage of a bot? * It never sleeps. * It has a perfect sense of timing. * It can have near perfect knowledge of updates to the blockchain. * It can instantly calculate an optimum response, numerically, to any formulaic input. Fixing the problem has to start with looking at those advantages and either giving them to humans or making them immaterial to the result. I say it a lot: "you get what you reward."
author | lextenebris |
---|---|
permlink | re-uberbrady-re-lextenebris-re-steemitblog-hardfork-20-velocity-development-update-20171221t014215877z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-21 01:42:15 |
last_update | 2017-12-21 01:42:15 |
depth | 3 |
children | 5 |
last_payout | 2017-12-28 01:42:15 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.119 HBD |
curator_payout_value | 0.032 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 5,018 |
author_reputation | 19,924,980,499,611 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,443,401 |
net_rshares | 24,819,059,941 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
valued-customer | 0 | 6,178,515,188 | 25% | ||
bronevik | 0 | 18,640,544,753 | 11% |
You have hit several nails right on their heads in this comment. >" Everyone is looking to jump on board the next big viral hit and playing the numbers to do so because the actual content doesn't matter..." HF20 doesn't even address this. This is clearly intentional, a feature, rather than a problem, to developers. >"...a shorter curation reward window actually rewards bots far more than human beings, who are much more likely to discover the existence of the post or comment well outside of a 30 minute window." Outside of any conceivable window. A window of any kind treats bots preferentially. Bots are able to be completely prevented from voting on the Steem blockchain. What I discovered in discussions with influential Steemers about this was that the more influential and powerful the account of the conversant, the more horrible the idea of eliminating bots appeared to be to them. We cannot vote without a key. A tripartite mechanism which a) delivers a private key to the blockchain with each post or comment, b) provides a public key which is necessary to enable a vote on that post or comment, can be, c) concealed within a captcha on the post or comment. This would virtually eliminate all voting by bots. After more than a year of operation, myriad automated means of curating have been developed, and most users depend on them. Those that are either not willing, or not able, to use automated curation leave. Of the accounts opened in 2016 but ~11% remained active as of Nov. 2017, and this includes bots, and multiples. No more than 10% of people that opened an account on Steemit in 2016, and probably less than 5% of them, remain on Steemit today. This should be revelatory. At least 90% of people that came to Steemit and opened an account, interested in a social media platform and new cryptocurrency rewards mechanism would be interested in a platform that didn't feature either a) bots and automated curation, b) oligarchical concentration and control of rewards, or c) some combination of those with other perceived problems of Steemit, such as it's flagging/censorship mechanism, UI, or so forth. Where would Farkbork be today if it had such user retention? Youtool? Twatter? The world is ripe for a social media platform that rewards content creators fairly. People are waiting for that platform today, and HF20 won't deliver it. Worst of all, Farkbork just acquired Charlie Lee's stake in Litecoin. ZuckerBorg is about to start monetizing likes. Steemit's window of opportunity may already have closed.
author | valued-customer |
---|---|
permlink | re-lextenebris-re-steemitblog-hardfork-20-velocity-development-update-20171220t232221423z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-20 23:22:36 |
last_update | 2017-12-20 23:22:36 |
depth | 2 |
children | 8 |
last_payout | 2017-12-27 23:22:36 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 2,561 |
author_reputation | 356,453,873,649,652 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,428,837 |
net_rshares | 3,151,044,220 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
lextenebris | 0 | 3,151,044,220 | 22% |
author | bronevik |
---|---|
permlink | re-valued-customer-re-lextenebris-re-steemitblog-hardfork-20-velocity-development-update-20171221t023115122z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-21 02:29:54 |
last_update | 2017-12-21 02:29:54 |
depth | 3 |
children | 0 |
last_payout | 2017-12-28 02:29:54 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 1.044 HBD |
curator_payout_value | 0.343 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 68 |
author_reputation | 12,260,156,653,305 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,448,763 |
net_rshares | 223,562,653,105 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
blow | 0 | 5,094,257,481 | 100% | ||
bronevik | 0 | 218,468,395,624 | 100% |
> Outside of any conceivable window. A window of any kind treats bots preferentially. I absolutely agree with that, 100% There are a couple of other really important "windows" associated directly with the STEEM blockchain which need to go the way of all flesh, in my opinion. The big one is the "seven day reward window." Why can content only be rewarded within seven days? We clearly have the technology to know if someone upvotes content which is older than seven days. We can upvote content which is older than seven days, and that vote goes into the blockchain as an indicator on the piece. Why shouldn't content which is useful outside of a seven day window continue to receive fiscal rewards as long as people keep upvoting it? As I say a lot: "you get what you reward." What does this reward? It rewards people both writing and consuming content like bots. It rewards bots farming content because they know it simply won't matter beyond the seven-day window. It actively works against the creation of content which is intended to be evergreen, to be useful, to be updated in the future. To tie in an unrelated thread, it makes "publish or perish" an inherent part of the ecosystem – on every front end that uses the STEEM blockchain. There is no planning for future use. There is no intention of future use. The entire blockchain becomes prioritized as ephemeral, disposable content. As you said about chasing the Dragon of viral content, "this is clearly intentional, a feature, rather than a problem, to developers." Personally, I think this is a terrible idea. > ... c) concealed within a captcha on the post or comment. > > This would virtually eliminate all voting by bots. That may be a bit of an optimistic view, given recent advances in automated solving of captcha problems and the fact that, at many levels, the STEEM blockchain is screaming out for an implementation of the Mechanical Turk. In fact, a lot of the "work contract" systems that I've seen some very prominent advocates on the blockchain promoting is simply a Mechanical Turk system without using the name. Now, that is not to say that I don't think such systems have their place and, in fact, that they can't be quite useful – but they certainly make it more complicated to say without question that this process would virtually eliminate all voting by bots. > After more than a year of operation, myriad automated means of curating have been developed, and most users depend on them. Those that are either not willing, or not able, to use automated curation leave. Well, I'm still around – but I'm a relative newbie. Worse, I'm a creator, which I occasionally feel is considered the worst kind of scum in the Steemit ecology, somehow ruining the purity of the reign of money from on high to those who can best optimize their interaction with the mechanics because I have the weird compulsion to make things and attract upvotes from the lesser lights in the world. I'm not really interested in using automated curation because automated curation doesn't care about content, and I care about content. I have this crazy idea of that rewards should be for the people that make stuff and for the people that help me find stuff that I'm likely to like – you know, what the word "curator" means everywhere else in the world. But that's not what it means here. On Steemit, "curator" means "someone willing to bet some temporary personal power on whether a piece of content will go viral throughout the community, no matter whether they like it, whether it's content that someone else will like, or even what it is. It's a bet of temporary power that will pay off or not within seven days – and the whole thing is a massive betting pool. That's what it is. If we're honest with ourselves, that's with the mechanics overtly encourage. > Where would Farkbork be today if it had such user retention? Youtool? Twatter? We have to point out a huge difference between Steemit and Facebook/YouTube/Twitter. In this is a major issue that I haven't seen anyone else take up. The mainstream, successful social networks are successful in part because their engagement makes for a virtuous cycle. People go to Facebook, they do so deliberately because they know people there, they engage with those people which are the reason that they came, they are exposed in that process to other people outside of that immediate circle, some of those people interest them or their work interests them, they Like or +1 or in some way signal to the system that's the sort of thing they like, and they immediately began to get more things that they are likely to enjoy. Immediately. Not after a month of shouting into the void. Not after having to go chase new people they don't know on a variety of live chats. This is a bigger problem than just "how fast can you make a new account," though that certainly doesn't help. The problem is rooted in the fact that there is nothing for them to do or reason to stay around, for the most part. If you look at people who are placed in a new social environment, you will notice that less than 10% of them choose any particular social outlet in any given context. Do we expect that someone that moves to a new area will go to a bar full of strangers and pick that is the first place they want to stop? Especially if the bartender refuses to serve them until they have hung out there for a month? No. That would be stupid. And yet… And yet. > The world is ripe for a social media platform that rewards content creators fairly. The really frustrating thing is that the social network of your imagination could be built on this platform. The tools are there. The underpinning is there. Maybe the infrastructure isn't quite ready for it, but some of the core ideas are there. It's just that nobody involved has ever had anything to do or care about social networks. You know how I know this? Because anybody with a decent criticism talks about Facebook, YouTube, and Twitter as if they are abominations, as if they have nothing useful to offer. Newsflash: they're winning. Newsflash #2: they will continue to win, without fail, as long as people keep referring to them with goofy little nicknames instead of looking at them as serious, hard-core players who are more than capable of observing an up-and-coming competitor and adopting every single thing about them that makes them special while maintaining the vast, almost incomprehensible network effect advantage that they have. That would be a shame. Or rather it would be a shame to let that pass without seeing the problem. > Worst of all, Farkbork just acquired Charlie Lee's stake in Litecoin. ZuckerBorg is about to start monetizing likes. Steemit's window of opportunity may already have closed. As a creator, you know what the funny thing is? I don't care. I can create things anywhere and share them anywhere else. I am perfectly capable of writing articles directly on Steemit and then sharing them to all the places I have a network presence – including Facebook, Twitter, Google+, Gab, and Minds. And I do! From the perspective of a creator who just wants to get paid for his work and doesn't really have any personal investment in a particular mechanism for that to occur? I have no reason to care. In fact, if Facebook builds a Steemit-like monetization system, then I can keep posting on Steemit for the superior Markdown editor for longform content, get my STEEM rewards, cross post to Facebook, get my Facebook rewards, and have all the advantages of both platforms. Not the least of which will be the fact that I will actually be able to spend my Facebook tokens on something worthwhile to me. Without jumping through a stack of flaming hoops in order to get some use out of it. That would immediately put it ahead of the STEEM blockchain. Downplaying the role of creators is one of the things that really hurts Steemit. They sell the platform as "a place where creators can get fairly compensated," and then build a mechanical architecture which is almost entirely absent of any sort of connection with content at all. In fact, it dis-incentivizes caring about content that you like in favor of trying to figure out what everybody else who is trying to figure out what everybody else will like will like. If that sounds confusing, welcome to being a new user on Steemit. Is it any wonder retention is under 10%? No. That's no mystery at all.
author | lextenebris |
---|---|
permlink | re-valued-customer-re-lextenebris-re-steemitblog-hardfork-20-velocity-development-update-20171221t021758594z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-21 02:17:57 |
last_update | 2017-12-21 02:17:57 |
depth | 3 |
children | 6 |
last_payout | 2017-12-28 02:17:57 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.028 HBD |
curator_payout_value | 0.006 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 8,441 |
author_reputation | 19,924,980,499,611 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,447,390 |
net_rshares | 6,178,515,188 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
valued-customer | 0 | 6,178,515,188 | 25% |
https://steemit.com/ned/@libertyranger/ned-this-user-is-destroying-steemit-do-you-even-give-a-shit
author | libertyranger |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171227t140853576z |
category | steem |
json_metadata | {"tags":["steem"],"links":["https://steemit.com/ned/@libertyranger/ned-this-user-is-destroying-steemit-do-you-even-give-a-shit"],"app":"steemit/0.1"} |
created | 2017-12-27 14:08:51 |
last_update | 2017-12-27 14:08:51 |
depth | 1 |
children | 0 |
last_payout | 2018-01-03 14:08:51 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 98 |
author_reputation | 7,267,049,896,950 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 25,518,855 |
net_rshares | 0 |
>After discussion with the witnesses, it was decided to apply the “vote dust” shift to all votes equally. Each vote that is cast will be shifted down by about 1.219 SP. This effectively establishes a “baseline” voting strength that applies to everyone, while still maintaining a linear rewards curve for votes above the baseline. This way even large Steem Power holders won’t be able to profit from casting countless inconsequential votes. Few words... I think this will create a sort of iniquity. The splitting up of big upvote is better of a 100% upvote to a lucky author (Perhaps his friend).
author | miti |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171220t195420182z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-20 19:54:21 |
last_update | 2017-12-20 19:54:21 |
depth | 1 |
children | 2 |
last_payout | 2017-12-27 19:54:21 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.194 HBD |
curator_payout_value | 0.064 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 599 |
author_reputation | 435,902,954,694,677 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,404,982 |
net_rshares | 41,766,912,112 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
abh12345 | 0 | 41,766,912,112 | 6% |
Agreed. But I am unsure of the numbers here. My 1% vote at around 18,000 SP is worth 4 cents. Is 4 cents not enough to gain some curation rewards in almost all cases, even if it is 0.001? It's not that I wish for any curation with that vote weight, I just choose to share my vote out. If it is now even more profitable curation-wise not to do this, are we not likely to see less votes going out to newer members?
author | abh12345 |
---|---|
permlink | re-miti-re-steemitblog-hardfork-20-velocity-development-update-20171220t214538573z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-20 21:45:39 |
last_update | 2017-12-20 21:45:39 |
depth | 2 |
children | 1 |
last_payout | 2017-12-27 21:45:39 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.050 HBD |
curator_payout_value | 0.016 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 420 |
author_reputation | 1,406,693,817,263,870 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,417,944 |
net_rshares | 11,274,983,489 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
miti | 0 | 11,274,983,489 | 50% |
You said reflects my own thoughts precisely.
author | miti |
---|---|
permlink | re-abh12345-re-miti-re-steemitblog-hardfork-20-velocity-development-update-20171221t071146260z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-21 07:11:51 |
last_update | 2017-12-21 07:11:51 |
depth | 3 |
children | 0 |
last_payout | 2017-12-28 07:11:51 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 44 |
author_reputation | 435,902,954,694,677 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,479,667 |
net_rshares | 0 |
Why not reduce the number of posts daily per account to 3-4 to reduce the spam behavior and reward pool rape of bad players? They could post more but set the rule of the payout on the fifth blog to be 0. There have been many cases of bad actors doing this, so why not reduce the damage being done?
author | moon32walker |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171221t114430493z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-21 11:44:30 |
last_update | 2017-12-21 11:44:30 |
depth | 1 |
children | 2 |
last_payout | 2017-12-28 11:44:30 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.339 HBD |
curator_payout_value | 0.003 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 300 |
author_reputation | 149,463,019,364,353 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,510,239 |
net_rshares | 55,470,676,606 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
moon32walker | 0 | 55,470,676,606 | 10% |
The way hardforks are determined is through a process of consensus. Proposals are made by community members, witnesses assess their quality, we help develop the code. These are the changes that have been agreed to based on a consensus process.
author | andrarchy |
---|---|
permlink | re-moon32walker-re-steemitblog-hardfork-20-velocity-development-update-20171222t172501916z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-22 17:25:00 |
last_update | 2017-12-22 17:25:00 |
depth | 2 |
children | 1 |
last_payout | 2017-12-29 17:25:00 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 243 |
author_reputation | 230,168,201,522,782 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,729,193 |
net_rshares | 0 |
Is there a formal process for community members to submit proposals? What are required steps?
author | slavix |
---|---|
permlink | re-andrarchy-re-moon32walker-re-steemitblog-hardfork-20-velocity-development-update-20171226t232820905z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-26 23:28:21 |
last_update | 2017-12-26 23:28:21 |
depth | 3 |
children | 0 |
last_payout | 2018-01-02 23:28:21 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 94 |
author_reputation | 27,303,148,571,540 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 25,418,818 |
net_rshares | 0 |
thank @steemitblog for the information you provide. very good information and useful for myself
author | my451r | ||||||
---|---|---|---|---|---|---|---|
permlink | re-steemitblog-20171221t0474762z | ||||||
category | steem | ||||||
json_metadata | {"tags":["steem","steemit","steemdev","hf20","hardfork"],"app":"esteem/1.5.0","format":"markdown+html","community":"esteem"} | ||||||
created | 2017-12-20 17:47:51 | ||||||
last_update | 2017-12-20 17:47:51 | ||||||
depth | 1 | ||||||
children | 0 | ||||||
last_payout | 2017-12-27 17:47:51 | ||||||
cashout_time | 1969-12-31 23:59:59 | ||||||
total_payout_value | 0.000 HBD | ||||||
curator_payout_value | 0.000 HBD | ||||||
pending_payout_value | 0.000 HBD | ||||||
promoted | 0.000 HBD | ||||||
body_length | 95 | ||||||
author_reputation | 430,156,339,377,869 | ||||||
root_title | "Hardfork 20 (“Velocity”) development update" | ||||||
beneficiaries |
| ||||||
max_accepted_payout | 1,000,000.000 HBD | ||||||
percent_hbd | 10,000 | ||||||
post_id | 24,387,324 | ||||||
net_rshares | 2,286,999,178 | ||||||
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
my451r | 0 | 2,286,999,178 | 100% |
Exciting times, great work guys - Steem on Steemians and look forward to the changes coming into effect. Do we have a proposed timeline for when the SMT's will come online @steemitblog, @teamsteem or anyone?
author | nikonmarshall |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171221t121013121z |
category | steem |
json_metadata | {"tags":["steem"],"users":["steemitblog","teamsteem"],"app":"steemit/0.1"} |
created | 2017-12-21 12:10:12 |
last_update | 2017-12-21 12:10:12 |
depth | 1 |
children | 0 |
last_payout | 2017-12-28 12:10:12 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 207 |
author_reputation | 1,767,086,451,496 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,513,342 |
net_rshares | 0 |
thanks for the update, may bring goodness for us all and success greetings.
author | nm007 |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171221t172047034z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-21 17:20:48 |
last_update | 2017-12-21 17:20:48 |
depth | 1 |
children | 0 |
last_payout | 2017-12-28 17:20:48 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 75 |
author_reputation | 471,530,141,203 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,557,911 |
net_rshares | 0 |
>In order to eliminate this unfair advantage, the unused portion of the curation rewards will be returned to the rewards pool instead of being awarded to the author What is, "the unused portion of the curation rewards"?
author | orenshani7 | ||||||
---|---|---|---|---|---|---|---|
permlink | re-steemitblog-20171222t114723731z | ||||||
category | steem | ||||||
json_metadata | {"tags":["steem","steemit","steemdev","hf20","hardfork"],"app":"esteem/1.5.0","format":"markdown+html","community":"esteem"} | ||||||
created | 2017-12-22 09:47:27 | ||||||
last_update | 2017-12-22 09:47:27 | ||||||
depth | 1 | ||||||
children | 0 | ||||||
last_payout | 2017-12-29 09:47:27 | ||||||
cashout_time | 1969-12-31 23:59:59 | ||||||
total_payout_value | 0.000 HBD | ||||||
curator_payout_value | 0.000 HBD | ||||||
pending_payout_value | 0.000 HBD | ||||||
promoted | 0.000 HBD | ||||||
body_length | 220 | ||||||
author_reputation | 25,008,785,557,132 | ||||||
root_title | "Hardfork 20 (“Velocity”) development update" | ||||||
beneficiaries |
| ||||||
max_accepted_payout | 1,000,000.000 HBD | ||||||
percent_hbd | 10,000 | ||||||
post_id | 24,668,697 | ||||||
net_rshares | 0 |
hey man, *pardon the off-topic comment…* I made a post today regarding a large-scale idea to advance Steem’s development, and it was recommended to share with the witnesses to help get this in front of the audience who’d be in the position to do something with/about it. came across your profile, and figured you might also be in contact with some power-players who'd appreciate this: <h3> [The $1 Billion Steem Development Fund: How Steemit Inc.'s Stake Could Be Best Allocated To Grow A Thriving Network Of Applications And Users...](https://steemit.com/steemit/@rok-sivante/the-usd1-billion-steem-development-fund-how-steemit-inc-s-stake-could-be-best-allocated-to-grow-a-thriving-network-of) </h3> would be cool if you could have a read, and **IF** you feel it’d be a great idea that’d serve the community, forward to anyone in particular you know who might be in a position of influence to advance the discussion. either way, I thank you for your continued service to this community. 🙏 cheers, Rok
author | rok-sivante |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20180208t043701555z |
category | steem |
json_metadata | {"tags":["steem"],"links":["https://steemit.com/steemit/@rok-sivante/the-usd1-billion-steem-development-fund-how-steemit-inc-s-stake-could-be-best-allocated-to-grow-a-thriving-network-of"],"app":"steemit/0.1"} |
created | 2018-02-08 04:37:03 |
last_update | 2018-02-08 04:37:03 |
depth | 1 |
children | 0 |
last_payout | 2018-02-15 04:37:03 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 1,013 |
author_reputation | 664,045,451,891,191 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 35,826,163 |
net_rshares | 0 |
You can find Russian version of this post [HERE](https://steemit.com/steem/@rusteemitblog/khardfork-20-velocity-skorost-informaciya-o-razrabotke-steemitblog) --- Русская версия [тут](https://steemit.com/steem/@rusteemitblog/khardfork-20-velocity-skorost-informaciya-o-razrabotke-steemitblog)
author | rusteemitblog |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171225t155822289z |
category | steem |
json_metadata | {"tags":["steem"],"links":["https://steemit.com/steem/@rusteemitblog/khardfork-20-velocity-skorost-informaciya-o-razrabotke-steemitblog"],"app":"steemit/0.1"} |
created | 2017-12-25 15:58:24 |
last_update | 2017-12-25 15:58:24 |
depth | 1 |
children | 0 |
last_payout | 2018-01-01 15:58:24 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 294 |
author_reputation | 35,289,965,594,592 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 25,190,338 |
net_rshares | 0 |
This are some exciting news. Now lets see how it will affect the whole community and the rewards 😉
author | sergiomendes |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171227t022237109z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-27 02:22:33 |
last_update | 2017-12-27 02:22:33 |
depth | 1 |
children | 0 |
last_payout | 2018-01-03 02:22:33 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 98 |
author_reputation | 678,677,025,848,084 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 25,436,160 |
net_rshares | 0 |
I really hope in steemit .
author | shweyaungmyanmar |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171222t020414007z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-22 02:04:27 |
last_update | 2017-12-22 02:04:27 |
depth | 1 |
children | 0 |
last_payout | 2017-12-29 02:04:27 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 26 |
author_reputation | 2,544,287,527,962 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,619,016 |
net_rshares | 0 |
I'm very new to Steemit and don't understand all of this. Resteeming as reminder to re-read and reference.
author | somethinfishy |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171226t231340293z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-26 23:13:45 |
last_update | 2017-12-26 23:13:45 |
depth | 1 |
children | 0 |
last_payout | 2018-01-02 23:13:45 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 108 |
author_reputation | 1,395,015,386,198 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 25,417,284 |
net_rshares | 593,783,800 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
somethinfishy | 0 | 593,783,800 | 100% |
Hope the updates will make steemit better than before & bring a lot of new users
author | sonny.dharmawan |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171223t160351847z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-23 16:03:39 |
last_update | 2017-12-23 16:03:39 |
depth | 1 |
children | 0 |
last_payout | 2017-12-30 16:03:39 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.368 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 80 |
author_reputation | 4,687,110,866,713 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,880,785 |
net_rshares | 66,432,018,077 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
sonny.dharmawan | 0 | 66,432,018,077 | 100% |
I didn't understand something, maybe someone can explain: . The Decincentivizing low votes... does it mean I can no longer vote like 3% votes?I didn't get it.
author | spiritualmax |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171226t232538608z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-26 23:25:36 |
last_update | 2017-12-26 23:25:36 |
depth | 1 |
children | 0 |
last_payout | 2018-01-02 23:25:36 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 159 |
author_reputation | 25,078,515,289,162 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 25,418,520 |
net_rshares | 0 |
thank you for this information and information is very useful for me and of course I will notify him to his steemian friends in the NSC community and other communities in Indonesia
author | steem77 |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171220t194616550z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-20 19:46:54 |
last_update | 2017-12-20 19:46:54 |
depth | 1 |
children | 0 |
last_payout | 2017-12-27 19:46:54 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 180 |
author_reputation | 6,746,680,658,188 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,404,019 |
net_rshares | 0 |
Thank you for the update, it looks like some positive steps to me! and one quick question based on quote below. "the unused portion of the curation rewards will be returned to the rewards pool instead of being awarded to the author" Does the above mean that 25% of the self upvote would be returned to the reward pool if the "upvote post" box was checked when posting?
author | steemitadventure |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171220t174305459z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-20 17:43:03 |
last_update | 2017-12-20 17:43:27 |
depth | 1 |
children | 10 |
last_payout | 2017-12-27 17:43:03 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 1.165 HBD |
curator_payout_value | 0.142 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 372 |
author_reputation | 38,702,956,343,359 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,386,629 |
net_rshares | 208,984,150,200 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
tarazkp | 0 | 52,853,684,453 | 4% | ||
destinysaid | 0 | 68,705,828,202 | 29% | ||
surprisebit | 0 | 4,834,773,839 | 100% | ||
steemitadventure | 0 | 21,164,530,720 | 16% | ||
steemreports | 0 | 14,412,223,218 | 50% | ||
inquiringtimes | 0 | 43,226,814,132 | 17% | ||
stingr4y | 0 | 472,173,300 | 100% | ||
fahry | 0 | 56,172,557 | 100% | ||
nikonmarshall | 0 | 3,257,949,779 | 100% | ||
iamleaf | 0 | 0 | 0% |
his beautiful postings, stop by my account and upvote him
author | fahry |
---|---|
permlink | re-steemitadventure-re-steemitblog-hardfork-20-velocity-development-update-20171220t180218348z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-20 18:02:30 |
last_update | 2017-12-20 18:02:30 |
depth | 2 |
children | 0 |
last_payout | 2017-12-27 18:02:30 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 57 |
author_reputation | 201,277,499,272 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,389,606 |
net_rshares | -17,468,462,707 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
techslut | 0 | -17,468,462,707 | -2% |
> Does the above mean that 25% of the self upvote would be returned to the reward pool if the "upvote post" box was checked when posting? Exactly. Users voting before the then 15 minute mark give up a share to the author. And if the author is responsible for that to happen, his part is returned to the pool. In my opinion a great change!
author | reggaemuffin |
---|---|
permlink | re-steemitadventure-re-steemitblog-hardfork-20-velocity-development-update-20171220t175552235z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-20 17:55:51 |
last_update | 2017-12-20 17:55:51 |
depth | 2 |
children | 8 |
last_payout | 2017-12-27 17:55:51 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 1.729 HBD |
curator_payout_value | 0.386 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 339 |
author_reputation | 37,964,839,695,531 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,388,619 |
net_rshares | 338,279,033,959 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
gruber | 0 | 11,565,077,917 | 70% | ||
destinysaid | 0 | 144,971,722,674 | 53% | ||
stormriderstudio | 0 | 9,492,166,602 | 61% | ||
steemitadventure | 0 | 21,164,530,720 | 16% | ||
steemreports | 0 | 14,579,807,208 | 50% | ||
inquiringtimes | 0 | 136,505,728,838 | 54% |
That is a good change @reggaemuffin and @techslut although I'm not sure I agree with dis-incentivising the use of many votes spread over different posts. It makes it harder for simple single photo posts to gain traction and yet photos can sometimes speak the most words. Photojournalism is part of where my interest lies and I believe this platform could compete with the likes of Instagram instead of focusing on the long form, this also provides incentive for newsbyte style articles instead of rewarding the longer posts the most. The reduced window to 15 minutes is a step in the right direction and I hope it continues to go that way. Love your work guys, keep it up and if any of you are in Australia I would love to meet up.
author | nikonmarshall |
---|---|
permlink | re-reggaemuffin-re-steemitadventure-re-steemitblog-hardfork-20-velocity-development-update-20171221t121605928z |
category | steem |
json_metadata | {"tags":["steem"],"users":["reggaemuffin","techslut"],"app":"steemit/0.1"} |
created | 2017-12-21 12:16:06 |
last_update | 2017-12-21 12:16:33 |
depth | 3 |
children | 2 |
last_payout | 2017-12-28 12:16:06 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 731 |
author_reputation | 1,767,086,451,496 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,514,096 |
net_rshares | 0 |
It would be perfect if that checkbox for self-upvoting vanished off the face of the steemit, IMHO. Would discourage self-voting at least a bit, I think.
author | techslut |
---|---|
permlink | re-reggaemuffin-re-steemitadventure-re-steemitblog-hardfork-20-velocity-development-update-20171220t180249875z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-20 18:02:48 |
last_update | 2017-12-20 18:02:48 |
depth | 3 |
children | 4 |
last_payout | 2017-12-27 18:02:48 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.096 HBD |
curator_payout_value | 0.032 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 152 |
author_reputation | 111,778,832,002,739 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,389,651 |
net_rshares | 21,228,655,882 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
thing-2 | 0 | 21,228,655,882 | 100% |
I think I like this update, but I'm guessing that the 'Upvote post' tick-box should be removed from condenser so that authors don't accidentally waste their voting power by using it?
author | steemreports |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171220t181553017z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-20 18:15:51 |
last_update | 2017-12-20 18:15:51 |
depth | 1 |
children | 3 |
last_payout | 2017-12-27 18:15:51 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 182 |
author_reputation | 26,974,091,964,123 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,391,567 |
net_rshares | 0 |
It is not completely a waste of their voting power, as they would still be giving themselves author rewards.
author | timcliff |
---|---|
permlink | re-steemreports-re-steemitblog-hardfork-20-velocity-development-update-20171221t063800314z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-21 06:38:00 |
last_update | 2017-12-21 06:38:00 |
depth | 2 |
children | 2 |
last_payout | 2017-12-28 06:38:00 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.076 HBD |
curator_payout_value | 0.022 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 108 |
author_reputation | 272,954,445,077,789 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,476,076 |
net_rshares | 16,423,231,108 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
steemreports | 0 | 16,423,231,108 | 50% |
Oh yes, that's true, I missed that! So this just means if you want to pay yourself, then you'll also pay a kind of bad behaviour tax to the rewards pool ;)
author | steemreports |
---|---|
permlink | re-timcliff-re-steemreports-re-steemitblog-hardfork-20-velocity-development-update-20171221t111226511z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-21 11:12:27 |
last_update | 2017-12-21 11:13:30 |
depth | 3 |
children | 1 |
last_payout | 2017-12-28 11:12:27 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.158 HBD |
curator_payout_value | 0.051 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 155 |
author_reputation | 26,974,091,964,123 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,506,578 |
net_rshares | 34,082,225,044 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
timcliff | 0 | 34,082,225,044 | 2% |
I just hope these changes prepare steemit for the big time and we can scale to millions of users.
author | steevc |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171226t185036647z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-26 18:50:39 |
last_update | 2017-12-26 18:50:39 |
depth | 1 |
children | 0 |
last_payout | 2018-01-02 18:50:39 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 97 |
author_reputation | 1,382,384,998,017,387 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 25,385,220 |
net_rshares | 0 |
Why payout declined?
author | sumsum007 |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171227t072145186z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-27 07:21:51 |
last_update | 2017-12-27 07:21:51 |
depth | 1 |
children | 0 |
last_payout | 2018-01-03 07:21:51 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 20 |
author_reputation | 42,926,659,872 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 25,468,196 |
net_rshares | 0 |
Nice
author | sumsum007 |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20180102t174301696z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2018-01-02 17:43:06 |
last_update | 2018-01-02 17:43:06 |
depth | 1 |
children | 0 |
last_payout | 2018-01-09 17:43:06 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 4 |
author_reputation | 42,926,659,872 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 26,604,620 |
net_rshares | 0 |
> HF20 will reduce this window from 30 to 15 minutes. I think this will help, humans complete better vs the bots. Thanks.
author | surprisebit |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171220t182911593z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-20 18:28:27 |
last_update | 2017-12-20 18:28:27 |
depth | 1 |
children | 0 |
last_payout | 2017-12-27 18:28:27 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.028 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 122 |
author_reputation | 3,263,883,552,712 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,393,459 |
net_rshares | 4,771,158,394 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
surprisebit | 0 | 4,771,158,394 | 100% |
I spent many hours curating and my sbd is being delegated. How can i change that and get paid for my long hours?
author | sweetjoy |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171231t234727148z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-31 23:47:39 |
last_update | 2017-12-31 23:47:39 |
depth | 1 |
children | 0 |
last_payout | 2018-01-07 23:47:39 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 113 |
author_reputation | 527,997,377,893 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 26,288,899 |
net_rshares | 0 |
The 30-minute curation window does nothing to stop bots. The bots just make sure to jump in right at the 30-minute mark. Changing the window to 15 minutes will not eliminate this problem. The window should be discarded entirely. And redistributing the curation rewards that happen in said 15-minute window will penalize the average Steemian who makes sure to check their "Upvote Post" checkbox whenever they compose a new post. Bad form, gentlemen.
author | talanhorne |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171220t173835211z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-20 17:38:36 |
last_update | 2017-12-20 17:38:36 |
depth | 1 |
children | 14 |
last_payout | 2017-12-27 17:38:36 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.509 HBD |
curator_payout_value | 0.162 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 453 |
author_reputation | 50,099,191,018,703 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,385,942 |
net_rshares | 107,553,352,792 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
inquiringtimes | 0 | 104,654,392,109 | 42% | ||
lextenebris | 0 | 2,898,960,683 | 22% |
The bots come in anywhere from 15-30 from what I see on my posts. I suspect many will opt now to change this down to 15 minutes. Hopefully this will increase congestion even further and the manual voter will win.
author | abh12345 |
---|---|
permlink | re-talanhorne-re-steemitblog-hardfork-20-velocity-development-update-20171220t213955358z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-20 21:39:54 |
last_update | 2017-12-20 21:39:54 |
depth | 2 |
children | 0 |
last_payout | 2017-12-27 21:39:54 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 214 |
author_reputation | 1,406,693,817,263,870 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,417,298 |
net_rshares | 0 |
This window is not an ideal solution by any means. But we have no better option still.
author | bronevik |
---|---|
permlink | re-talanhorne-re-steemitblog-hardfork-20-velocity-development-update-20171221t020839833z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-21 02:07:18 |
last_update | 2017-12-21 02:07:18 |
depth | 2 |
children | 0 |
last_payout | 2017-12-28 02:07:18 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 1.088 HBD |
curator_payout_value | 0.360 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 86 |
author_reputation | 12,260,156,653,305 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,446,166 |
net_rshares | 233,889,694,138 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
bronevik | 0 | 233,889,694,138 | 100% |
I disagree. The window allows more fair play. I could make a bot that votes all posts of successful authors in the first second. Or i could build a bot that makes a tradeoff between voting early or late and the incentive is already not there anymore. And the self vote change means that the author can't take curation rewards into his own pocket, a change that will hurt mostly whales. And honestly, you should never expect to get that 25% curation as an author in the first place.
author | reggaemuffin |
---|---|
permlink | re-talanhorne-re-steemitblog-hardfork-20-velocity-development-update-20171220t175836885z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-20 17:58:36 |
last_update | 2017-12-20 17:58:36 |
depth | 2 |
children | 5 |
last_payout | 2017-12-27 17:58:36 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.700 HBD |
curator_payout_value | 0.168 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 482 |
author_reputation | 37,964,839,695,531 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,389,035 |
net_rshares | 139,370,547,426 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
steemreports | 0 | 14,579,807,208 | 50% | ||
sanjeevm | 0 | 6,629,308,579 | 10% | ||
tipu | 0 | 39,270,391,595 | 20% | ||
juicy-shark | 0 | 78,891,040,044 | 100% |
> I could make a bot that votes all posts of successful authors in the first second You can't because there are more than 10 successful authors posting daily, and besides you will be competing with other bots for a share (likely small) of those authors if you're all voting on the same ones. It rapidly becomes diminshishing returns and a waste of your vote power. > Or i could build a bot that makes a tradeoff between voting early or late That's exactly what happens now under the 30 minute (or 15 minute rule). Bots are able to time things exactly and make calculated vote timing, while humans are disadvantaged unless they stare at a clock and act like a bot.
author | smooth |
---|---|
permlink | re-reggaemuffin-re-talanhorne-re-steemitblog-hardfork-20-velocity-development-update-20171220t192319900z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-20 19:23:21 |
last_update | 2017-12-20 19:23:51 |
depth | 3 |
children | 4 |
last_payout | 2017-12-27 19:23:21 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 2.050 HBD |
curator_payout_value | 0.619 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 666 |
author_reputation | 253,602,537,834,068 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,400,962 |
net_rshares | 428,067,855,858 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
blocktrades | 0 | 405,999,458,919 | 1% | ||
ratel | 0 | 9,739,091,778 | 40% | ||
arcange | 0 | 6,811,356,019 | 1% | ||
raphaelle | 0 | 950,272,184 | 1% | ||
whatsup | 0 | 0 | 1% | ||
randomwhale | 0 | 1,226,130,617 | 100% | ||
dahlsom | 0 | 3,281,404,133 | 100% | ||
rayken04 | 0 | 60,142,208 | 10% |
I agree with you that the rule is not helpful and should be even shorter or removed altogether. However, there isn't consensus including the stakeholders and dev team to do that. While the reduction to 15 minutes isn't my ideal choice here, I do feel it is a clear improvement. While you are right it does little about bots other than cause them to make a small recalibration, it does penalize humans less, even when voting before 15 minutes. For example, under the 30 minute rule, voting after 10 minutes would reduce curation rewards by 66% while now it will only reduce them by 33%,
author | smooth |
---|---|
permlink | re-talanhorne-re-steemitblog-hardfork-20-velocity-development-update-20171220t192127900z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-20 19:21:42 |
last_update | 2017-12-20 19:21:42 |
depth | 2 |
children | 0 |
last_payout | 2017-12-27 19:21:42 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 2.379 HBD |
curator_payout_value | 0.730 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 588 |
author_reputation | 253,602,537,834,068 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,400,713 |
net_rshares | 498,257,075,112 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
blocktrades | 0 | 405,999,381,008 | 1% | ||
kenny-crane | 0 | 63,502,446,296 | 15% | ||
ratel | 0 | 9,870,701,126 | 40% | ||
arcange | 0 | 6,811,356,019 | 1% | ||
raphaelle | 0 | 950,272,184 | 1% | ||
valued-customer | 0 | 6,599,777,587 | 25% | ||
randomwhale | 0 | 1,251,411,660 | 100% | ||
dahlsom | 0 | 3,211,587,024 | 100% | ||
rayken04 | 0 | 60,142,208 | 10% |
> The 30-minute curation window does nothing to stop bots. The bots just make sure to jump in right at the 30-minute mark. What if after 30 min window the post was already heavy upvoted and the curation reward for the bot will be minimal? That's the whole idea, without the 15 min windows bots will just upvote in the first second. Than the curation rewards for humans will be very low. We want the opposite.
author | tipu |
---|---|
permlink | re-talanhorne-re-steemitblog-hardfork-20-velocity-development-update-20171220t204523144z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-20 20:45:24 |
last_update | 2017-12-20 20:45:51 |
depth | 2 |
children | 3 |
last_payout | 2017-12-27 20:45:24 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 409 |
author_reputation | 55,921,946,728,577 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,411,083 |
net_rshares | 0 |
Exactly!
author | reggaemuffin |
---|---|
permlink | re-tipu-re-talanhorne-re-steemitblog-hardfork-20-velocity-development-update-20171221t063541562z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-21 06:35:39 |
last_update | 2017-12-21 06:35:39 |
depth | 3 |
children | 0 |
last_payout | 2017-12-28 06:35:39 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.151 HBD |
curator_payout_value | 0.012 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 8 |
author_reputation | 37,964,839,695,531 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,475,805 |
net_rshares | 26,654,992,045 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
tipu | 0 | 26,654,992,045 | 15% | ||
minnowboosted | 0 | 0 | -100% |
What we want is curation rewards for actual, significant curation to be higher. Camping for the top posters and waiting to vote (whether after 5-10 minutes or immediately) is not the quality curation that we want to reward humans for doing. I'm perfectly happy letting bots get that (relatively small) portion of the pool and letting humans go elsewhere to curate harder-to-find content. This situation was very different in the early days with less content, fewer voters, and n^2 rewards. In that environment, the vast majority of the rewards (both posting and curation) went to just a tiny handful of posts from a tiny handful of authors. That's no longer the case.
author | smooth |
---|---|
permlink | re-tipu-re-talanhorne-re-steemitblog-hardfork-20-velocity-development-update-20171221t110255100z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-21 11:02:57 |
last_update | 2017-12-21 11:03:21 |
depth | 3 |
children | 1 |
last_payout | 2017-12-28 11:02:57 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.028 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 668 |
author_reputation | 253,602,537,834,068 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,505,492 |
net_rshares | 4,786,803,187 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
randomwhale | 0 | 1,226,130,617 | 100% | ||
dahlsom | 0 | 3,560,672,570 | 100% |
15min is clearly more reasonable than 30min so humans can compete better with bots. It was discussed and many were of your opinion but it was easier to just change a parameter and has less risk of unintended consequences. Even if it was to take 30min to read an article it usually doesn't take more than 15min to get a good feel of the value of a post. Also given 10 votes a day as optimal voting frequency it's less likely anyone would actually spend 5 hours a day (30min*10) reviewing content than 2.5h.
author | transisto |
---|---|
permlink | re-talanhorne-re-steemitblog-hardfork-20-velocity-development-update-20171220t175538014z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-20 17:55:39 |
last_update | 2017-12-20 17:55:39 |
depth | 2 |
children | 0 |
last_payout | 2017-12-27 17:55:39 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 176.354 HBD |
curator_payout_value | 57.983 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 507 |
author_reputation | 330,357,940,720,833 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,388,598 |
net_rshares | 37,404,710,654,471 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
gtg | 0 | 43,495,209,553 | 1% | ||
transisto | 0 | 10,073,390,333,404 | 100% | ||
tamim | 0 | 10,915,393,961,205 | 100% | ||
maryfavour | 0 | 8,932,326,644 | 1% | ||
newsflash | 0 | 16,195,711,546,966 | 100% | ||
steemreports | 0 | 14,747,391,199 | 50% | ||
inquiringtimes | 0 | 152,431,397,202 | 62% | ||
yakuza | 0 | 0 | -100% | ||
donaldpatterson | 0 | 608,488,298 | 100% |
> In order to eliminate this unfair advantage, the unused portion of the curation rewards will be returned to the rewards pool instead of being awarded to the author, thereby increasing the overall percentage of rewards that will be paid to curators. This is clearly better than what we have today. I really love this brilliant idea. I'm eager to see how it will pan out. That being said I don't expect much of an effect on those who give themselves 100% of their votes. They will simply do it on comments after the 15 minutes marks.
author | teamsteem |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171220t204742512z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-20 20:47:39 |
last_update | 2017-12-20 20:47:39 |
depth | 1 |
children | 3 |
last_payout | 2017-12-27 20:47:39 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 1.530 HBD |
curator_payout_value | 0.496 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 538 |
author_reputation | 284,804,541,406,803 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,411,333 |
net_rshares | 325,691,044,864 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
andrarchy | 0 | 185,379,151,873 | 7% | ||
abh12345 | 0 | 22,781,952,061 | 3% | ||
destinysaid | 0 | 68,705,828,202 | 29% | ||
preparedwombat | 0 | 14,770,426,378 | 4% | ||
sircork | 0 | 0 | 100% | ||
juicy-shark | 0 | 34,053,686,350 | 44% |
There's at least one immediate beneficial effect against self-voting: before their curation rewards turned into author rewards (SBD) because of the shifting effect, now those curation rewards will be steem power.
author | blocktrades |
---|---|
permlink | re-teamsteem-re-steemitblog-hardfork-20-velocity-development-update-20171220t224721461z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-20 22:47:18 |
last_update | 2017-12-20 22:47:27 |
depth | 2 |
children | 1 |
last_payout | 2017-12-27 22:47:18 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.110 HBD |
curator_payout_value | 0.032 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 212 |
author_reputation | 1,285,246,364,327,926 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,425,041 |
net_rshares | 23,427,079,619 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
abh12345 | 0 | 22,785,349,830 | 3% | ||
ergiegonzaga | 0 | 641,729,789 | 100% |
It's another really good plus I haven't thought about. By the way I'm very grateful for your dedication to the development of Steem. I've been living and breathing Steem since May 2016 day in and day out. So thank you!
author | teamsteem |
---|---|
permlink | re-blocktrades-re-teamsteem-re-steemitblog-hardfork-20-velocity-development-update-20171220t230518074z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-20 23:05:15 |
last_update | 2017-12-21 05:16:09 |
depth | 3 |
children | 0 |
last_payout | 2017-12-27 23:05:15 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.106 HBD |
curator_payout_value | 0.032 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 219 |
author_reputation | 284,804,541,406,803 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,426,937 |
net_rshares | 22,785,349,830 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
andrarchy | 0 | 0 | 0% | ||
abh12345 | 0 | 22,785,349,830 | 3% |
its an amazing initiative indeed. at the very least, accounts with major SP that self upvote in the first 15 mins will have a good amount of reward as curation returning to the reward pool instead of themselves. As for self voting comments, thats rather easy to catch, and cant self voters be ousted via pulling data from the blochchain? I think someone does that.
author | destinysaid |
---|---|
permlink | re-teamsteem-re-steemitblog-hardfork-20-velocity-development-update-20171220t230518767z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-20 23:05:24 |
last_update | 2017-12-20 23:05:24 |
depth | 2 |
children | 0 |
last_payout | 2017-12-27 23:05:24 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 366 |
author_reputation | 47,671,849,857,331 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,426,950 |
net_rshares | 0 |
> Each vote that is cast will be shifted down by about 1.219 SP. This effectively establishes a “baseline” voting strength that applies to everyone, while still maintaining a linear rewards curve for votes above the baseline. This way even large Steem Power holders won’t be able to profit from casting countless inconsequential votes. I am not sure I understand that. Can anyone clarify?
author | techslut |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171220t173947638z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-20 17:39:48 |
last_update | 2017-12-20 17:39:48 |
depth | 1 |
children | 28 |
last_payout | 2017-12-27 17:39:48 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.321 HBD |
curator_payout_value | 0.107 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 389 |
author_reputation | 111,778,832,002,739 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,386,123 |
net_rshares | 68,705,828,202 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
destinysaid | 0 | 68,705,828,202 | 29% |
it looks like if i have around 100 SP and vote you with 100% weight, my vote towrds you goes as if i had voted with 98.781 SP. Why? Not 100% sure, but seems like people could spam ultratiny votes
author | furious-one |
---|---|
permlink | re-techslut-re-steemitblog-hardfork-20-velocity-development-update-20171220t180104064z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-20 18:01:00 |
last_update | 2017-12-20 18:01:00 |
depth | 2 |
children | 0 |
last_payout | 2017-12-27 18:01:00 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.321 HBD |
curator_payout_value | 0.107 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 196 |
author_reputation | 119,528,603,711,317 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,389,402 |
net_rshares | 68,705,828,202 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
destinysaid | 0 | 68,705,828,202 | 29% | ||
steembusiness | 0 | 0 | 30% |
This means that if you have 100 SP and you do a vote, you effectively vtoe with 98.8 SP. That means one 100% vote is better than two 50% votes, reducing the reward on 0.01% votes spammed. I don't think that that one SP will make a lot of a difference but the general idea sounds good.
author | reggaemuffin |
---|---|
permlink | re-techslut-re-steemitblog-hardfork-20-velocity-development-update-20171220t174950476z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-20 17:49:48 |
last_update | 2017-12-20 17:49:48 |
depth | 2 |
children | 26 |
last_payout | 2017-12-27 17:49:48 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.217 HBD |
curator_payout_value | 0.025 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 284 |
author_reputation | 37,964,839,695,531 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,387,635 |
net_rshares | 38,935,052,370 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
vladikras | 0 | 4,269,026,545 | 37% | ||
greer184 | 0 | 15,868,037,503 | 100% | ||
costopher | 0 | 12,758,195,185 | 48% | ||
satfit | 0 | 4,249,587,988 | 61% | ||
humanabstract | 0 | 1,790,205,149 | 100% |
> This means that if you have 100 SP and you do a vote, you effectively vtoe with 98.8 SP > Each vote that is cast will be shifted down by about 1.219 SP. Your explanation (per user) semantically contradicts with the blog post above (per vote). Awaiting clarification.
author | liberosist |
---|---|
permlink | re-reggaemuffin-re-techslut-re-steemitblog-hardfork-20-velocity-development-update-20171220t182407749z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-20 18:24:12 |
last_update | 2017-12-20 18:25:15 |
depth | 3 |
children | 2 |
last_payout | 2017-12-27 18:24:12 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 270 |
author_reputation | 177,167,275,265,899 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,392,807 |
net_rshares | 0 |
I tend to vote a lot but at low percentages. Wouldn't this change encourage people to be "stingy" with smaller votes? If I am making more off 100% posts, then why should I give 10% to 100 posts if I can get more by giving 100% to 10 posts? Or am I getting the math very wrong (again)?
author | techslut |
---|---|
permlink | re-reggaemuffin-re-techslut-re-steemitblog-hardfork-20-velocity-development-update-20171220t180146680z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-20 18:01:45 |
last_update | 2017-12-20 18:01:45 |
depth | 3 |
children | 12 |
last_payout | 2017-12-27 18:01:45 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 284 |
author_reputation | 111,778,832,002,739 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,389,510 |
net_rshares | 0 |
I like that it create a larger incentive for smaller stake holder to own more Steem. I find 1.219 SP to be quite an odd number.
author | transisto |
---|---|
permlink | re-reggaemuffin-re-techslut-re-steemitblog-hardfork-20-velocity-development-update-20171220t175941286z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-20 17:59:42 |
last_update | 2017-12-20 17:59:42 |
depth | 3 |
children | 9 |
last_payout | 2017-12-27 17:59:42 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 171.138 HBD |
curator_payout_value | 57.035 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 128 |
author_reputation | 330,357,940,720,833 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,389,198 |
net_rshares | 36,428,542,410,713 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
transisto | 0 | 9,859,062,879,501 | 100% | ||
tamim | 0 | 10,697,086,081,980 | 100% | ||
newsflash | 0 | 15,871,797,316,027 | 100% | ||
yakuza | 0 | 0 | -100% | ||
donaldpatterson | 0 | 596,133,205 | 100% |
I see this being WAY better for self upvoters than those who use the platform the way it's intended. We need a hardfork that will disincentivize people paying bots to take rewards no one else agreed they should have.
author | thatsweeneyguy |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171220t182328985z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-20 18:23:27 |
last_update | 2017-12-20 18:23:27 |
depth | 1 |
children | 0 |
last_payout | 2017-12-27 18:23:27 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.028 HBD |
curator_payout_value | 0.009 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 216 |
author_reputation | 27,446,015,260,706 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,392,712 |
net_rshares | 6,599,777,587 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
valued-customer | 0 | 6,599,777,587 | 25% |
Great publication well done
author | tohamy7 |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171220t184112248z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-20 18:41:12 |
last_update | 2017-12-20 18:41:12 |
depth | 1 |
children | 0 |
last_payout | 2017-12-27 18:41:12 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 27 |
author_reputation | 8,807,709,091,999 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,395,308 |
net_rshares | 0 |
It will all shake out as the technology catches up with the content creators and curators.
author | tonygreene113 |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171221t103104614z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-21 10:28:57 |
last_update | 2017-12-21 10:28:57 |
depth | 1 |
children | 0 |
last_payout | 2017-12-28 10:28:57 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.061 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 90 |
author_reputation | 24,136,017,318,625 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 0 |
post_id | 24,501,340 |
net_rshares | 10,011,890,081 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
tonygreene113 | 0 | 10,011,890,081 | 100% |
Can we finally win the battle of the dust vote? Posted using [Partiko Android](https://steemit.com/@partiko-android)
author | tonygreene113 |
---|---|
permlink | tonygreene113-re-steemitblog-hardfork-20-velocity-development-update-20180909t133124880z |
category | steem |
json_metadata | {"app":"partiko"} |
created | 2018-09-09 13:31:24 |
last_update | 2018-09-09 13:31:24 |
depth | 1 |
children | 0 |
last_payout | 2018-09-16 13:31:24 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 118 |
author_reputation | 24,136,017,318,625 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 70,788,729 |
net_rshares | 0 |
I just checked in for Partiki and made an easy 10 points. Posted using [Partiko Android](https://steemit.com/@partiko-android)
author | tonygreene113 |
---|---|
permlink | tonygreene113-re-steemitblog-hardfork-20-velocity-development-update-20180909t133236043z |
category | steem |
json_metadata | {"app":"partiko"} |
created | 2018-09-09 13:32:36 |
last_update | 2018-09-09 13:32:36 |
depth | 1 |
children | 0 |
last_payout | 2018-09-16 13:32:36 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 127 |
author_reputation | 24,136,017,318,625 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 70,788,828 |
net_rshares | 0 |
Why are you not giving updates on SMT launch ?? Custom applications with their own way of rewarding will save steem from such bots. 15 min 30 min time frame is just a waste of time for humans. Bots are much more intelligent than humans. They can vote on 15.01 min but humans can't. I think we have to remove SP with reward relationship. Just tie SP with bandwidth. The more SP you have the more you can post. If we talk about reward, 1 upvote = certain fixed amount irrespective of whatever amount of SP you have. Your vote will count as 1 (with fixed voting reward)
author | vikasjaat |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171220t195912383z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-20 19:59:15 |
last_update | 2017-12-20 19:59:15 |
depth | 1 |
children | 3 |
last_payout | 2017-12-27 19:59:15 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 570 |
author_reputation | 167,288,028,053 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,405,582 |
net_rshares | 651,766,568 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
vikasjaat | 0 | 651,766,568 | 100% |
> Why are you not giving updates on SMT launch ?? Their last update was that it would be available sometime early 2018. There is a lot of activity in GitHub for it. I suspect they will announce when they have something to announce.
author | timcliff |
---|---|
permlink | re-vikasjaat-re-steemitblog-hardfork-20-velocity-development-update-20171221t010701075z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-21 01:07:00 |
last_update | 2017-12-21 01:07:00 |
depth | 2 |
children | 2 |
last_payout | 2017-12-28 01:07:00 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 232 |
author_reputation | 272,954,445,077,789 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,439,630 |
net_rshares | 0 |
@timcliff I was hoping it would come along side the HF 20,so apparently we might see different launches? I am also not seeing communities in this, but I am going to check the other update. @vikasjaat, removing SP and tethering posts to bandwidth would be a very terrible idea, besides, changing monetary policies is sure to cause some court cases to pop up except stated when bringing in investors.
author | destinysaid |
---|---|
permlink | re-timcliff-re-vikasjaat-re-steemitblog-hardfork-20-velocity-development-update-20171221t040044183z |
category | steem |
json_metadata | {"tags":["steem"],"users":["timcliff","vikasjaat"],"app":"steemit/0.1"} |
created | 2017-12-21 04:00:48 |
last_update | 2017-12-21 04:00:48 |
depth | 3 |
children | 1 |
last_payout | 2017-12-28 04:00:48 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.076 HBD |
curator_payout_value | 0.025 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 399 |
author_reputation | 47,671,849,857,331 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,459,059 |
net_rshares | 16,986,181,006 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
timcliff | 0 | 16,986,181,006 | 1% |
Unexpected changes, let's see how they improve the platform
author | vispasian |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171220t173033468z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-20 17:30:33 |
last_update | 2017-12-20 17:30:33 |
depth | 1 |
children | 0 |
last_payout | 2017-12-27 17:30:33 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 59 |
author_reputation | 9,821,322,962,721 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,384,738 |
net_rshares | 870,455,810 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
vispasian | 0 | 93,139,781 | 100% | ||
givonwayne | 0 | 777,316,029 | 100% |
Thank you for the news, looks inspiring. What is exactly "PoW mining for discounted accounts" and which accounts are discounted?
author | vitkolesnik |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171220t180806582z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-20 18:08:06 |
last_update | 2017-12-20 18:08:06 |
depth | 1 |
children | 2 |
last_payout | 2017-12-27 18:08:06 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 128 |
author_reputation | 16,545,270,223,382 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,390,461 |
net_rshares | 0 |
There is info on this in the original announcement post. There is a link to it in the post above.
author | timcliff |
---|---|
permlink | re-vitkolesnik-re-steemitblog-hardfork-20-velocity-development-update-20171221t063705572z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-21 06:37:06 |
last_update | 2017-12-21 06:37:06 |
depth | 2 |
children | 1 |
last_payout | 2017-12-28 06:37:06 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 97 |
author_reputation | 272,954,445,077,789 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,475,968 |
net_rshares | 603,174,397 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
slowgrow | 0 | 603,174,397 | 100% |
Thank you, found it.
author | vitkolesnik |
---|---|
permlink | re-timcliff-re-vitkolesnik-re-steemitblog-hardfork-20-velocity-development-update-20171221t162923887z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-21 16:29:24 |
last_update | 2017-12-21 16:29:24 |
depth | 3 |
children | 0 |
last_payout | 2017-12-28 16:29:24 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.076 HBD |
curator_payout_value | 0.025 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 20 |
author_reputation | 16,545,270,223,382 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,550,243 |
net_rshares | 17,041,190,430 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
timcliff | 0 | 17,041,190,430 | 1% |
I do self vote my posts and I think you did a great thing modifying the situation! Curators needs to have more reward while people are voting for them so I will be pleased to "lose" my curation reward while self voting to pass it to the curators! Great job! In regards of "_Each vote that is cast will be shifted down by about 1.219 SP. This effectively establishes a “baseline” voting strength that applies to everyone, while still maintaining a linear rewards curve for votes above the baseline. This way even large Steem Power holders won’t be able to profit from casting countless inconsequential votes._" it is not very clear to me how it will work... could you please explain it slightly better?
author | webdeals |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171221t082214288z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-21 08:22:15 |
last_update | 2017-12-21 08:22:15 |
depth | 1 |
children | 0 |
last_payout | 2017-12-28 08:22:15 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 702 |
author_reputation | 410,373,804,154,165 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,487,434 |
net_rshares | 0 |
Looking forward to seeing how these will impact the community! Thank You for keeping us informed!
author | weetreebonsai |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171220t174425321z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-20 17:44:24 |
last_update | 2017-12-20 17:44:24 |
depth | 1 |
children | 0 |
last_payout | 2017-12-27 17:44:24 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 97 |
author_reputation | 2,145,502,320,998 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,386,828 |
net_rshares | 0 |
Thank you for the news
author | zacknight |
---|---|
permlink | re-steemitblog-hardfork-20-velocity-development-update-20171220t182514717z |
category | steem |
json_metadata | {"tags":["steem"],"app":"steemit/0.1"} |
created | 2017-12-20 18:20:21 |
last_update | 2017-12-20 18:20:21 |
depth | 1 |
children | 0 |
last_payout | 2017-12-27 18:20:21 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 22 |
author_reputation | -689,546,549,483 |
root_title | "Hardfork 20 (“Velocity”) development update" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 24,392,244 |
net_rshares | 0 |