Ah sorry, you are totally right, quasimodo. A glitch in my human text reading unit *lol*. My bad. I confused the STAKEHOLDER BOUNTY with the NODE BOUNTY. Thanks for clarifying. Question to the HZ team: Shall I start a second instance of my BAMM.py, and also start monitoring NHZ-XB5G-QDAG-NU3M-EL8L8 ?
|
|
|
AltSheets B.E.E.f.Acopy of my 4 postings in the HZ thread
Block explorer extension for assetAltsheets, after your previous posting about the asset transaction deficit prompted me to examine the leading NXT explorers (my fav has been https://nxtblocks.info/ which much to my dismay I just learned is shutting-down - announcement on their homepage) it occurred to me that this indeed appears to be a needed extension of the Horizon explorer. Therefore if the community sees fit to crowdfund that I would support it. Thx. I'd love to see that work out. Will publish the source these days! Thanks, mavigro, for supporting of my idea. Such feedback is honey for my soul :-) And thanks, pharesim, for the code, and helping me to install it on my server, great! As usual, and like many times before, I am disappointed that almost no one reacted to this: Anyone wants to pledge some crowd bounty for it?
... but that seems to reflect the state of the crypto subculture. Egoistic. Money has a very bad influence on the otherwise beautiful human soul. We should consider as a species ... if we can afford to stick to capitalism as such. However, the lack of donations ... has not kept me from doing it ! And ... YIEHAH, I SUCCEEDED! - I installed the existing source code (creating a mini manual for it),
and ran the backend (took ~36 hours on my small droplet!)
- Then today, "learnt PHP" for it.
And deciphered the existing code structure, whew.
- and then implemented my new page asset.phtml,
and extended it with many useful little ideas, and improvements.
keep tuned ...
Block Explorer Extension for Assets ...
B.E.E.f.A - quick start:So that you can see live what I have coded, I put it on a (weak!) server of mine (only until it will be pulled upstream). Isn't that great? --> Now you can get the issuance information (including the text description) for all HZ assets, just by changing that long 19-digits id number in the above URL. Try it out - e.g. post links to your favorite asset here ...
B.E.E.f.A - quick start: ... Block explorer extension for assetsSuggestion: Warnings about certain assetsIn the past there have already been discussions about blacklisting assets - which I do not want to repeat here. Me personally, I am strongly opposed to any kind of censorship. "Caveat emptor (Buyer beware)" is a more grown up concept than the childish "Consumer protection by censorship and prohibition". A good option is whitelisting assets (see the HZ " trusted assets" page), but there are yet only 4, and I always thought ... ... "what about all the other 100+ HZ assets out there"? That is why I built my extension asset.phtml. I would want it to always display all assets ... scam, test, or proper ... regardless. What is on the blockchain, gets reported!But still -especially where without any doubts- I consider ADDITIONAL information is appropriate ... if a certain asset should rather not be bought. Good thinking? So this is what I coded, to implement a first approximation of that idea: asset warningsSome assets are known to be test assets, or revoked (by the issuer), or even scams ( perhaps, probably or proven scams). However, the (too) centralized power of the only official block explorer ... needs a balance between user protection and issuer protection (and censorship is bad)! So with my new 'asset.phtml' extension ... all assets are still shown - but in some cases with a clear warning. All is hardcoded into an XML file. I urge the team to always link back to a forum post where detailed explanations are given, and can be discussed - so that e.g. the issuer gets a chance to react to the suspicion. examples for the different warnings:To be totally clear: Almost all assets will show none of those warnings - because they are intended to be, and run as proper assets. What do you think about that suggested system? P.S.: This whole "warnings" function is already coded now, but it can be easily ignored completely. My extension works well without filling in that 'assetwarnings.xml'. If you find it too much to worry about for now ... just go back to the "quick start" posting above now..
This is just a copy-for-eternity, to document it here on my AltSheets timeline. Please do discuss it over there in the HZ thread, or in the Horizon Forum, not here ! Thx :-)
|
|
|
Can you still edit the poll? What about adding a forth option to vote for:
* bittrex implements a technical solution: each user can store a one-per-coin return target address, in case the coin gets de-listed
Then, when I have invested into a coin which I want to hodl (or auto-sell in a possible rally - that's why I keep them on the exchange in the first place, in a high-price sell order) ...
... I simply download the wallet, make a new address, copy that address into a new field on my bittrex webpage.
Done. And then I can go sailing happily across the Pacific for 6 months, or into the Amazonian jungle, or on top of the Himalayas - without fear that my coins will get de-listed in the meantime.
---
EDIT: Who needs the authorities when a simple technical solution can fully solve a problem? EDIT2: Will not work for broken coins, when the blockchain is stuck, but those are only a few.
|
|
|
What is the newspaper stand?
Read the OP and the 1st edition ( edition #01 copy), then you'll understand better perhaps. It is an overview of different news outlets, big and small, about the crypto world. How can it benefit me as dev of 2bacco coin?
What can I do with it?
I give that question back to you: I am very interested to read how you make that useful for yourself. Please study it a bit, then think about it, and give feedback, please. Thanks a lot!
|
|
|
B.E.E.f.A - quick start: ... Block explorer extension for assetsSuggestion: Warnings about certain assetsIn the past there have already been discussions about blacklisting assets - which I do not want to repeat here. Me personally, I am strongly opposed to any kind of censorship. "Caveat emptor (Buyer beware)" is a more grown up concept than the childish "Consumer protection by censorship and prohibition". A good option is whitelisting assets (see the HZ " trusted assets" page), but there are yet only 4, and I always thought ... ... "what about all the other 100+ HZ assets out there"? That is why I built my extension asset.phtml. I would want it to always display all assets ... scam, test, or proper ... regardless. What is on the blockchain, gets reported!But still -especially where without any doubts- I consider ADDITIONAL information is appropriate ... if a certain asset should rather not be bought. Good thinking? So this is what I coded, to implement a first approximation of that idea: asset warningsSome assets are known to be test assets, or revoked (by the issuer), or even scams ( perhaps, probably or proven scams). However, the (too) centralized power of the only official block explorer ... needs a balance between user protection and issuer protection (and censorship is bad)! So with my new 'asset.phtml' extension ... all assets are still shown - but in some cases with a clear warning. All is hardcoded into an XML file. I urge the team to always link back to a forum post where detailed explanations are given, and can be discussed - so that e.g. the issuer gets a chance to react to the suspicion. examples for the different warnings:To be totally clear: Almost all assets will show none of those warnings - because they are intended to be, and run as proper assets. What do you think about that suggested system? P.S.: This whole "warnings" function is already coded now, but it can be easily ignored completely. My extension works well without filling in that 'assetwarnings.xml'. If you find it too much to worry about for now ... just go back to the "quick start" posting above now..
|
|
|
Block Explorer Extension for Assets ...
B.E.E.f.A - quick start:So that you can see live what I have coded, I put it on a (weak!) server of mine (only until it will be pulled upstream). Isn't that great? --> Now you can get the issuance information (including the text description) for all HZ assets, just by changing that long 19-digits id number in the above URL. Try it out - e.g. post links to your favorite asset here ...
|
|
|
Block explorer extension for assetAltsheets, after your previous posting about the asset transaction deficit prompted me to examine the leading NXT explorers (my fav has been https://nxtblocks.info/ which much to my dismay I just learned is shutting-down - announcement on their homepage) it occurred to me that this indeed appears to be a needed extension of the Horizon explorer. Therefore if the community sees fit to crowdfund that I would support it. Thx. I'd love to see that work out. Will publish the source these days! Thanks, mavigro, for supporting of my idea. Such feedback is honey for my soul :-) And thanks, pharesim, for the code, and helping me to install it on my server, great! As usual, and like many times before, I am disappointed that almost no one reacted to this: Anyone wants to pledge some crowd bounty for it?
... but that seems to reflect the state of the crypto subculture. Egoistic. Money has a very bad influence on the otherwise beautiful human soul. We should consider as a species ... if we can afford to stick to capitalism as such. However, the lack of donations ... has not kept me from doing it ! And ... YIEHAH, I SUCCEEDED! - I installed the existing source code (creating a mini manual for it),
and ran the backend (took ~36 hours on my small droplet!)
- Then today, "learnt PHP" for it.
And deciphered the existing code structure, whew.
- and then implemented my new page asset.phtml,
and extended it with many useful little ideas, and improvements.
keep tuned ...
|
|
|
great work
Thanks. Anything you'd like added to it? how much does it cost after the trial?
Let's try this for now: Prices
0.15 BTC for 3 months 0.25 BTC for 6 months 0.40 BTC for 12 months
= "a quarter of a bitcoin for half a year"
good?
|
|
|
Thanks Altsheets, your Newstand effort prompted me to revisit my RSS subscriptions adding about 20 active feeds from your list and while doing-so I bubbled-up 20 that I'm watching not on your list captured here to a Google sheet w/Alexa metrics incl. Change, Site and Feed links. http://2020.fm/forasKudo's to all the outstanding content Creators that help make Cryptocurrency a fascinating arena to follow and participate in. Wow wow wow. That is amazing. Surpassing my expectations. Thanks a lot for that. So easy to merge with my existing table! Cool. Cooperation! I will include all of them into my next version. Which might still take some time, first I wait whoever else is adding to this. It is actually getting retweeted a bit at the moment: https://twitter.com/altsheets/status/612042042110308352Nice way of passing on the information. I have an idea: * Let's use your sheet for inputting added sites, in a structured way. * You just have to change the "share" option to "everyone who has the link ... can edit" * Perhaps add two more columns: "added by (nickname)", and "alexa numbers looked up on (date) ..." If you agree with that ... ... everyone who wants to add another site, please input it into the first empty line on: http://2020.fm/foras thanks.
|
|
|
re: trusted asset submission Hey Horizons Due to clever choices, my inbox with 838 emails is still spam free, hooray! And I would like to keep it that way. And still, I'd like to submit my asset. So two tiny issues: 1) The form only scrolls up to ASSET NAME / ASSET IDENTIFIER instead of scrolling up to the error message "the field Main Contact Email require a valid email address" It took very long until I had found that error message. 2) I will not input my address in a robot readable form email@domain.tldbecause that would be inviting spam address harvester robots ... but in a slightly obfuscated form email(at)domain(dot)tldwhich is still understandable for (90% of all) humans. But when I try that, the form does not get accepted. So I had to fill in a dummy value instead now - please PM me. Thanks!
|
|
|
|