When is a developer buying up against the sell wall something dishonest? especially as the currency has been steadily gaining and holding upward valuation over the last month, and none of the volume generated is coming from the premine you seemed to have a problem with. George remains, more than two years after genesis, an involved developer who is working to build an important social legacy with blockchain technology,  building something that will make a difference in the real world beyond the confines of cryptocurrency, to produce funding for HIV/AIDS research, LGBT advocacy, women's shelters...

again, this moves away for the core issue presented: POSW Holdings arbitrarily delisted his currency from their exchange and online staking wallet, with no warning to the developer, the GAYcoin community or the PoSWallet community. in doing so, they held onto a balance of George's *PERSONALLY OWNED ASSETS* which thru continued upward valuation, presently have a value in excess of one million dollars US. they have claimed that the funds mysteriously, and without transaction records, was transferrred to an account not controlled by poswallet, and have claimed there was a possible hack of the system.

for these funds to be supposedly transferred "off the exchange" without transaction records this would have needed to be done from within the exchange itself, thus any "hack" would have been against the exchange and not the GAYcoin wallet. they claimed that the GAYcoin developer purposefully hardforked the GAYcoin wallet, although im still using a wallet from prior to the "hack" and it remains on the correct blockchain, so another excuse that doesnt stand up to scrutiny.

this is simply a warning. poswallets administrators have shown the desire to remain anonymous, although they are in charge of large amounts of other people's money. we are asked to simply trust that they are honest. George placed his trust in the poswallet platform when he deposited 2.4 mln GAYcoin onto poswallet.com and should have had no issue in withdrawing it, even in small portions to conform to the withdrawl limits imposed at the exchange. when they released the private keys to his on-exchange wallets, they presented him with one inaccurate key, and his request for the correct privkey went unanswered.

George's deposit and withdrawl history, screenshot from poswallet.com supports his side of the story. (note timestamp from his computer on bottom right)

WITHDRAWLS: https://postimg.org/image/k85f57ubf/

DEPOSITS: https://postimg.org/image/3mucub19x/

CURRENT BALANCE: https://postimg.org/image/eoa96gy99/

George still requests the return of his funds, either the release of the wallet in GAYmoney itself, or the equivalence in another currency, preferably BTC.  POSW Holdings LLC needs to come clean with their identities and to explain how these funds were transferred internally, and if there was a "hack" which targeted only ONE wallet in ONE currency, why this information was not shared to the community as would be responsible for any company to do, considering their position as an FSB, and this violation of security on the exchange side of operations puts EVERYONE'S FUNDS AT RISK, no matter the denomination of currency they trust poswallet.com to hold on their behalf.

no, they lost 2.5 million of his personally held coins that he has purchased on exchange and staked with his own project.

the 5 bln premine has remained entirely untouched and intact from the genesis, and has nothing to do with the loss. those funds are set for funding LGBT and HIV/AIDS advocacy, research and awareness, and have noting to do with any developers reserve. even funds supplied to myself have been sent from the developers personal holdings. the fact that the premine has remained absolutely untouched for years should show that this isnt some shitcoin, they werent dumped on the exchange when listing was established a long time back. there is a plan for them, and there will be public input on how those funds are allocated, those details will be part of GAYmoney's new [ANN], and is immaterial towards the crux of the issue presented....

this is an issue regarding the theft of someone's funds, the lack of security FROM interference by an exchange against one's own wallet, regardless if they are the the developer of the project, or if the person experiencing the loss was a minor shareholder like myself at that point in time, we as customers must have the security that the funds we deposit on exchanges are safe. and when there IS an issue, that the exchange would be forthright and honest regarding the issue and not engage in evasive tactics.

the IDEA behind poswallet.com is a great one. but the developers needed to remain more connected and communicating with coin devs and communities, the massive delistings can only serve to lessen confidence in this exchange, but the idea... POOLED STAKING... is an important one and i sincerely hope that the administrators behind poswallet can deal with this problem in a transparent manner and find the impetus to continue their services as recognized individuals, and hopefully make sure that the number one priority is customer support. i hope poswallet can survive this, but they do have the responsibility to run their business in very specific ways to protect client (member) investments. if they cannot be counted on to do that, then hopefully a more responsible site will appear to take poswallets place.

the time for unregulated cryptocurrency exchanges is over

(TL/DR version: POSW Holdings LLC,, the owners of poswallet.com, thru intent or accident, have defrauded the developer of GAYcoin to the tune of nearly ONE MILLION DOLLARS USD.)

Id like to preface this by stating that I was an early adopter and booster of poswallet.com. With the push towards the more environmentally conscious Proof-of-Stake type currencies available, it was a great place to be able to start looking into a number of different alt-currencies I wouldve otherwise ignored, being able to stake them in a pooled setting. I began staking a little bit in a whole lot of different coins, POS wasnt a very comfortable concept to me, my experience being working with the EVM as one of the developers of SOILcoin. I used poswallet.com for months, not a single problem. I became an unpaid promoter, talking up the project online, to my friends, etc.

Fast forward to April 23rd of this year, and the events that have now led to the reason behind this open message to the cryptocurrency community. Without warning to the poswallet community, during a spate of announcements related to currency delistings scheduled for a few weeks down the road, one currency was simply completely and suddenly delisted from the exchange and the online staking wallet, without explanation. This was the currency GAYmoney.

Owing to the fact I had about 500 GAYcoins in my possession on poswallet.com, I wrote to the poswallet_admin on the slack channel to ask what had happened. I was informed that they had decided to delist the currency, and that they had credited user accounts with POSWcoin as a form of compensation. 500 GAY coins may not have been much, but Im not a rich investor, im on a small disability pension and cryptocurrency, even thru my own project's development, its never been something that was going to make me rich, but there is a principle involved in the matter which Ive been very vocal about in the past. I mentioned that there wasn't any record of POSW being credited to my account, and was informed it had been done "internally", so there was no transaction record per se.

Cryptocurrency exchanges NEED to be held to a higher standard, we the public have to put trust in them in order to hold our funds. When we place our digital assets on an online exchange, or pooled staking service like poswallet.com, you are placing trust in a group of people, in this case - a directorship that has publicly chosen to remain anonymous  - to hold your funds and not to misplace them, or do whatever they want with them.

I communicated this to the developer and admin of poswallet on their slack channel, and he agreed, finding a way to make sure that in the future, with currency delistings that could not be withdrawn in a typical fashion by whatever reason, that compensation would be verifiable and with transparent transactions. They agreed that open and honest communication between the exchange administrators and both supported currency developers and the community of users that use the service was a fundemental aspect going forward. poswallet_admin even commented that the exchange could use someone like me on board, working for them, and that they were going to be looking at their staffing needs going forward very soon.

All seemed fine, I even began reaching out to the developers and communities of the currencies that were on the delisting chopping block, to see if there was any way to save those currencies. For some, it seemed, poswallet had become a last refuge other than yobit, which has become notorious for its poor customer service. For others, they were abandoned by the developer, and didnt have a sustainable community - theyll be listed only in the necronomnicon threads going forward unfortunately, but still - i believe in supporting a healthy cryptocurrency ecosystem, and every project CAN have its merits.

I also got in touch with the developer of GAYmoney, GeorgeL. I just wanted to understand what the problem had been and to offer a bit of compassion, as a developer who has found the road to getting listed on reputable exchanges to be an arduous one, and having been delisted (due to volume) from the only exchange we were on... I understood the frustration from a personal level. I wound up having a great conversation with him. We talked about his plans giong forward for his project, how he wanted to rebrand it and start making good on the locked reserves he set aside during luanch years ago - to provide a philanthropic legacy for LGBT and HIV/AIDS advocacy and research as those funds became available. He had very ambitious plans going forward and a deep passion for his project. After talking with him over a few days I agreed to come on board to help build a community base for the project on the cryptocurrency side of the equation, and was also presented with a problem....

George had requested the funds he had deposited into poswallet.com in GAYmoney be returned to him, and the admin at PoSWallet returned a pair of private keys to him, one of which was connected to his account, the other one to was an empty, unused account. The private key to the GAY wallet he owned on poswallet, to which he requested the funds from, contains 2,483,738 GAY, a large part of his personal holdings, was not included. George sent me the private keys they had sent so that i could verify, and his problem was very accurate.

As he explained the situation, he had begun to withraw his large stake on the website, and very suddenly, the exchange simply deleted its listings for GAYmoney on its dashboard and on its exchange (although they left the market running for days afterward, via the link at coinmarketcap). He was accused of "forking the wallet" by the admin, and then was offered 30,000 POSWcoins in compensation for the currency that was now unaccessible. George sent me screen captures of his few deposits onto poswallet.com, as well as his withdrawals (and tx hashes) and current balances. There was record of his own deposits, but no record of the POSWcoin deposit. There was NO RECORD of him withdrawing the bulk of his wallet, although there were two confirmed withdrawals of a smaller amount of GAY. There was no current balance of POSWcoins in his current balance to support his having received any POSWcoins in compensation for the 2.4 mln GAY account.

He gave me permission to speak with poswallet.com's support and administration staff on his behalf regarding this, and while i have provided both entities with the transaction record of the initial deposits made by Gaymoney's dev onto poswallet.com AND the private keys they had sent to George as well as links to the wallets they own AND provided them George's email to contact him with the correct private key or to do the proper thing, rebuild their GAY wallet with the backup data that any responsible exchange would keep, and simply send a verifiable transactin from the wallet they have control of to a wallet address that we have provided.

A week of consistent contact on my part has been completely ignored by the admin of poswallet, and the support staff member on the slack channel assured me days ago that this problem would be taken care of right away but then maintained no further communication. When I finally mentioned a likely complaint to the Financial Crimes Enforcement Network, a subsiduary of the US Treasury Department, I got a response from the administrator on the slack channel. I was informed that they didn't own the GAY wallet the coins were in, that they were "somehow sent to an external wallet - either via a technical bug or via hacking". When I pointed out that it was his exchanges responsibility to maintain security, and if there had been a hack, they were duty bound to have reported it to the userbase rather than trying to cover it up. I insisted that GeorgeL be returned his funds, and was finally told "I think PoSWallet.com will have to shut down because of this.  We only have 1.2 BTC in funding (this project was a labor of love) - we can not afford to fight something that we have already settled."

I need a moment to put this problem into a monetary perspective, regardless of anyone's political beliefs regarding the currency itself. Currently the 7-day average price for GAYcoin has maintained a valuation between 16.000 and 22.000 satoshi... between USD$0.35-$0.45. The assumable value of the currency, based on the last transaction in BTC on the markets is 17.128 satoshi (approximately USD$0.39 based on a $2260 USD bitcoin at the time of writing) Presented as a value in bitcoin, the wallet being held by poswallet.com is worth 425.4 BTC. In US dollar value, this represents an assumable value, using the same unit price above for BTC, of USD $961,404. JUST UNDER A MILLION DOLLARS U.S.

George has been very upset about this, he has proof of deposit thru the blockchain, he has the public address to the wallet poswallet stored his funds on, supposedly securely, and has provided everything they would need to ensure that his assets, deposited in good faith, would be returned to him after the exchange arbitrarily and without notice, removed the currency from the exchange and dashboard, preventing him from retrieving the assets as would be his right, as would be ANYONES rights we should assume, in dealing with a supposedly reputable cryptocurrency exchange. Again, the spectres of Mt.Gox and Cryptsy rear their heads, and should we be surprised, dealing with an administration staff that chooses to remain anonymous. This is a stark reminder that the only coins you OWN are the ones you maintain the private keys to the wallet for. You can exercise evidenciary channels to prove ownership, but when dealing with a dishonest entity who maintains those keys, you have NO CONTROL over your own funds.

I have communicated the urgency and the value of this problem to both poswallet's admin and support staff on the slack channel and can provide saved copies of what has been sent to them, as well as the links thru the GAYmoney block explorer to the deposits made, and LEFT in stasis, I can provide screenshots of the GAYcoin developers poswallet.com account showing his deposits, his withdrawls and his balance, all of which can be independently verified thru the blockchain. PoSWallet has yet to provide any documentation to support their claims.

I have remained professional and looked for ANY SORT of constructive communication with the staff at poswallet in finding out, firstly: what went wrong, and secondly: how to fix it. This is a million dollar mistake on their part, and one might assume, something they would devote some time to soving and some constructive communication both to myself as the authorized representative for GAYmoney's developer or to GeorgeL, who held the account on poswallet.com in the first place.

They have failed to answer any question, they have failed to provide any documentation, they have failed to send any logfile requested showing the investigation they supposedly did to find out how George's funds were transferred to "an outside wallet" withough any transaction record (something that could only be done through an internal transaction, which admin already showed a capability of in supposedly sending POSWcoin compensation to currency holders in compensation without any transaction record), they have failed to send the private key to George's GAYmoney wallet that was removed from his ability to access by poswallets injudicious delisting and deletion of GAYmoney from their services without any prior notice. This is THEFT.

poswallet.com is registered as PoSWallet Holdings LLC in Youngsville, NC; and thus subject to the financial regulations enforced within the United States, and complaints regarding this situation will be filed with the Financial Crimes Enforcement Network (FinCEN). A lawsuit against PoSWallet Holdings LLC and its directors (Colin Blakely, Nathan Faust, Michail Douranos, and Petros Anagnostou) may be launched.

poswallet's terms and conditions state "PoSWallet makes no representation and does not warrant the safety of the Platform and is not liable for any lost value or stolen property, whether or not PoSWallet was negligent in providing the proper security." Yet, when poswallet ITSELF is behind the problem by deslisting the currency without warning, trapping every users funds originally placed into their care - when they misrepresent the private keys sent to the owners of those wallets - this isnt an issue of negligence in security, it begins to look like a case of actionable and possible criminal neglect on the part of the staff employed by poswallet, if not outright criminal enterprise. This contumacious action should be a simple fix. The adress in question: http://104.236.2.124:3001/address/gNWMUpHjwEvDEGZ2z56FdotCc4HgPQNfo6 must have its funds released by PoSWallet Holdings LLC back to the rightful owner, George Lawin. If these funds have been made unavailable because poswallet's staff irresponisbly did not maintain proper backups, they are responsible to rectify the situation by fully reimbursing the owner in another currency that is agreeable to that developer. (In this case - 425 BTC)

In fairness to the other side of the story, a short history of GAYmoney is helpful. It is a long extant cryptocurrency project, launched in 2014 by "GeorgeL", the developer. He set aside in the genesis block, and then locked up, a premine of 5 billion GAY coins that would be released in the future to LGBT and HIV/AIDS awareness, advocacy and ativism groups and individuals, with the plan of sustained philanthropic funding that will last decades. He has referred to this as his "legacy" and wants to help address social issues related to his currency's target market. This is less a simple  cloned altcoin and more of a social endowment coupled with a specialized digital currency targeting one of the most diverse markets on the planet. That reserve account remains locked and untouched in the GAY.foundation wallet (which is non-participatory in the staking consensus). link:http://104.236.2.124:3001/address/gLsrjEbo31wmXZQssAeGyrw4CwBZgxafev

While the project has remained under-the-radar for a long time - George faced initial resistance and bigotry when he made his original [ANN], a new one will be set out soon - there is a great deal of development underway for a sort of re-launch with new website, wallets, storefront partnerships, and a large scale philanthropic movement via the assosciated GAY.foundation to be ready by 3rd quarter of this year. A GAYmoney dedicated gateway for fiat and major cryptocurrency exchange markets is being investigated, which will eventually maintain an altcoin exchange dedicated to a strong sense of community with both developers and users and a focus on showcasing cryptocurrencies with socially consicious agendas. We will focus on building connections between the cryptocurrency community and the LGBT and HIV/AIDS aweness communities worldwide.

GAYmoney remains a tradable asset on Cryptopia, against BTC, LTC, DOGE and UNO and George is interested in pursuing further exchange integrations, although he wants to set the bar high for the reputation of the exchange, and has expressed great interest in co-operation on decentralized "atomic-trading" exchanges. We are presently taking the first steps in setting up an active community network on both sides of the digital divide to help make GAYmoney a stable and long-term humanitarian cryptocurrency with well established usage in the real world. If anyone wants to get involved with GAYmoney, and in helping build a decentralized, globally social-conscious network, please dont hesitate to contact me here on bitcointalk or via email at abvhiael@live.ca. The lead dev, George, can be reached at info@gaycoin.online as well.

Im hoping that in making this issue public that poswallet will be pressured into releasing George's funds to him in a timely and responsible manner, as any exchange would do given the unique circumstances of this situation, one that they themselves set into motion with their own actions. Please share it widely, and if you agree, please write to poswallet_admin and poswallet_support on the poswallet.slack.org channel, as well as on their website.

I dont know the full reasons behind the delisting of GAYmoney by poswallet, despite asking the admin why and not getting a response, and I wont put any political motivation behind those decisions without evidence. I wont engage in FUD because this situation could simply be a glitch on their part that they are trying to solve, but hoping to preserve pulic trust by remaining somewhat elusive while they put things back together. I can hope thats whats happening.

Beyond writing this, and informing the cryptocurrency community as a whole about the distressing lack of real support and also regarding the possible criminal behaviour by the administrators of poswallet.com and executives at PoSWallet Holdings LLC, I hope this impels the public to remove their funds held  on or trading on a service that shows a consistent trait of financial irresponsibility and a failure to live up to its promises until such time as the executives come clean regarding the missing funds in GAYmoney that they have thus far refused to release to its RIGHTFUL LEGAL OWNER.

I will be forwarding a complaint to FinCEN (Financial Crimes Enforcement Network), an agency of the US Department of the Treasury, to whom poswallet.com has applied for certification to operate as a MSB (Money Services Business). In this PoSWallet Holdings must, as both a virtual currency exchange and the administrators thereof are considered money transmitters, and must comply with rules to prevent money laundering/terrorist financing and other forms of financial crime, by verifiable record-keeping, accurate reporting and mandatory registerion. A Suspicious Activity Report (SAR) or Suspicious Transaction Report (STR) will be made, as the transactions by PoSWallet Holdings, and its exchange are very unusual for this particular sort of business, and appear to be done only for the purpose of hiding or obfuscating transactions or in-house negligence. By rights, the support staff should have ALREADY submitted an SAR as the transaction in question is aggregated to above $25.000, which is applicable to values of stocks, mutual funds, etc... and inclusive by definition with digital or virtual currencies.

PoSWallet has failed to provide any documentation regarding the deposits they supposedly made, or the log files for debugging the issue that would have been done. These funds were entrusted to them, and as operators of an exchange, they have failed in their fiduciary duties to safeguard them, and have acting grossly negligent and with criminal irresponsibility. A "constructive fraud claim", as defined by statutes in North Carolina is being investigated, as a cause of action exists, PoSWallet Holdings LLC and GeorgeL were in:
 (1) a relationship of trust and confidence,
 (2) that the defendant took advantage of that position of trust in order to benefit himself, and
 (3) that plaintiff was, as a result, injured.

Owing to it's registration as an LLC (Limited Liability Company) in North Carolina, PoSWallet Holdings is governed by the "North Carolina Limited Liability Company Act", as well as the Articles of Organization governing all LLCs in North Carolina. Colin Blakely, the registerer of POSW Holdings LLC (http://www.sosnc.gov/Search/filings/12639858) as manager and controlling shareholder, legally owes a fiduciary duty to minority shareholders. This fiduciary duty by a majority shareholder manager of an LLC is defined in North Carolina as the contract "to exercise reasonable care, skill, and diligence in the transaction of business entrusted to him, and he will be responsible to his principal for any loss resulting from his negligence in failing to do so."

Its time for exchanges to be held accountable, for the registered agents to be held responsible for their actions and neglect when acting as financial agents, and should not be allowed the comfort of anonymity. Ive also experienced smaller disappearances on poswallet.com, not for any amount approaching the theft of the GAYcoin wallet in question, but in the eyes of an exchange operator each single investment whould be equal as each represents the actual funds of a user placing trust in them. Im sure theres a thousand more tales of mismanagement at poswallet, from what ive seen on the troll box in the last few days, things are unravelling there in a hurry. Me, im taking every coin i can off that exchange before it closes its doors. And then, Ill be investigating the mechanisms required to begin actions, criminal and civil, against Colin Blakely and any other named manager of POSW Holdings LLC, on behalf of George Lawin, the lead developer of GAYmoney.

Sorry for the lengthy post, folks, but in cases like this, the facts must be presented in total to defer the oncoming FUD and insanity. Ive spent weeks trying to solve this issue with poswallet.com's staff, only to be gven excuses that might mollify someone new to cryptocurrency, but sound a whole lot like the first steps of an exit strategy to someone seasoned.
 

we wont know anything from bittrex until they decide one way or another. you can send a message to julian on the bittrex slack to help move things along if youd like. their SOIL wallet is up to date, theyve applied the latest patches, so you should have no problem moving SOIL off of bittrex onto a fully synced SOIL client.

ive been squirrelling away some currency from another project im working on and will be adding to our DOT balance at cryptopia, hopefully i can put enough in to help cover what we need to get listed there. im very much in pro-favour of having us listed at cryptopia, the support there is phenomenal, not only from the devs and admins that are online, but the folks in the troll box are very helpful too.

the best bet, as always, is to send a small test amount from bittrex to your wallet to be sure its synced correctly, and then send the rest over.

where this currency will maintain a decent enough valuation, at least likely a more or less stable one, thanks to its CoinAge requirements. ive been grabbing little bits here and there from the faucet, my oldest coins are now 5 days old, and theyre spaced out enough (pun intended) over the next few days that watching the staking mechanism of this currency ought to be fun. projects with similar overall designs, or even looser designs if you take ones like 808 (8 day coin age), seem to have a lasting permanence, so hopefully the devs can pass the pipe to the rest of us to keep development along a nice mellow curve. at the very least, its a fun project to watch, cant wait for more bounties to get big old lung-gagger "tokes" on my wallet every once in awhile.

this is a cute coin. i like the wallet. will you posting the winning wallets tx from the giveaway? i had 1000/5500 entries dammit. i never win anything. (chuckles) there was that time in middle school i won a raffle for a cake that looked like pacman though. will be watching for this to hit the exchanges and try to pick some up, my poor old computer is too ornery to do much mining.

is hyper 2.0 the new iteration of hyperstake? i know there was a HYP and a HYPER out there in the crypto wilderness, so sort of unclear which project this is the 2.0 version of....

Twitter account: www.twitter.com/SOILcoin
Bitcointalk Name: abvhiael
Twitter Audit: https://www.twitteraudit.com/SOILcoin
No. of Followers: 345

Retweets(WEEK1)
https://twitter.com/InternetOfCoins/status/860149895352778753
https://twitter.com/InternetOfCoins/status/860213090939539456
https://twitter.com/InternetOfCoins/status/863031134409695232


Unique Tweets (WEEK1)

ConCoin (CONX) is another recently released altcoin running a similar POW/POS hybrid system, producing POW distribution for the first K number of blocks before POS starts running properly, even though coins show as staking, and the countdown clock in the qt-wallet show nearly immediately impending stakes for days at a time. CONX doesnt switch to full POS until block 512.000

in a way, as an investor, its a good thing, because of other participants impatience, currencies experiencing this sort of delay get dumped hard and allow folks with some understanding to buy cheap. NOBT has a 10% APR, which is very sustainable. the dev has shown me thru daily conversations that he is very interested in building up his currency, providing services, and i believe he will be sticking with the project and shows a genuine curiosity to the underworkings of what hes built and what he can do with it going forward. and regardless of the code underlying the project, ANY project really, when you have a dev that shows a willingness to stand by his project, even during difficult points in its history, that is a project that CAN succeed.

im still staking the original airdropped amounts so its not like i have a big stake in this game, but id rather support new developers that show a willingness to learn and to stick with their project. ive agreed to help nobtcoin out where i can, when i can wrestle an hour or three away from my own project, (we've just upgraded out own codebase im major ways so its a lot of documenting and testing right now) and in that i understand the struggles and frustrations a lot of new devs go thru, trying to separate their project from the sheer weight of the scam coins.

this one deserves our support.

well, im three for three with the free roll tourneys... to be honest i know absolutely NOTHING about european football, the players or the teams so when i do luck into winning a few XFC from a tourney itll be celebration time for sure! would love to see this sort of tech scaled towards other sports. hey dev... you need someone to administer an NHL iteration for next season? im a hardcore hockey fan, and love this platform. eventually, ill even win a little at footballcoin.io. a very entertaining currency.

...hopefully this is the last of the update documentation for a little bit. (laughs) so many new implementations, so much more we're going to have to test going forward... this post should cover the last of the upgrades to the SOIL, as pushed in by the 1.6.0 (Puppeth Master) code updates to Ethereum, and which brings SOILcoin to simple parity with their codebase....

*puppeth* : a new CLI interface which assists building new Ethereum-level blockchain networks down to the genesis, bootnodes, signers, ethstats, faucet, dashboard, etc , eliminating the need configure all these services one by one. Puppeth uses ssh to dial into remote servers, and builds its network components out of docker containers using docker-compose. The user is guided through the process via a command line wizard which handles the background configurations. This will help build test-nets for dApp development or private blockchains for DAOs, and should be an integral part of the system building a cross-chain linked blockchain network in the future.

Alongside Puppeth, a consensus engine interface will be built into the network level protocols of go-soil. It will permit the usage of alternatives to POW block verification schemes for smaller networks, where a different security model may be required. With this release, two consensus models are supported in the production of private chains: the currently used POW model, ethash; and a new "Proof of Authority" model called clique.

Clique, the POA protocol works by allowing authorized signatories to create new blocks at their own discretion, with the ability to control minting frequency, minting distribution load between the full list of signatories, and to dynamically adjust the list of trusted signers as needed. This protocol would require for a predetermined number of signatories have active nodes at any one time, to ensure minting diversity.

As far as I understand it, from researching the consensus engine idea, these sorts of entities could be deployed as sub-chains and mineable tokens on the EVM, and as Casper (the Ethereum Core's Proof of Stake model) comes closer to implementation, its methods are likely to be included within this interface as well. Ethereum has released a testnet (Rinkeby) that is running the PoA consensus engine, https://www.rinkeby.io/ which features netstats, a github linked faucet, block explorer, etc. if you want to poke around an iteration of what Puppeth can build out from SOILcoin as well.

*smaller changes

The gsoil console command evm can be used to disassemble contracts, as well as to create contracts written in teh EVM assembly language.

The swarm implementation is expanded to also permit users to upload and download entire directories via tarball streams in the HTTP interface, as well as mount an entire folder structure into their local filesystem via FUSE.

RPC compiler calls (eth_compileSolidity, eth_compileSerpent, and eth_compileLLL) are deprecated, and dApp developers are urged to use "proper development tools" instead. (truffle, embark, dapple) [i honestly had nothing but grief using eth_compile* with any dApp development work ive done, and while theres a learning curve to the CLI development tools mentioned, user-friendliness is improving exponentially.

thats pretty much it for the updates to potentiality with the SOILcoin blockchain. there are a ton of adjunct dApps and contracts that have to be deployed in support of these changes, and over the next few weeks ill be deploying and documenting these as well. a great deal of testing and screwing about with Swarm and Whisper is going to be needed to be done, in order to present the most friendly and understandable guides to using these technologies.

The first suite that i have to look at implementing is our own SOILcoin Name Service, which will be an integral part of the swarm funtionality on the SOILnet. The SNS will eliminate the need to copy long hexadecimal addresses (0xa1b2C3d4Ef67aA...), allowing users to claim .soil addresses, so that a transaction can be sent to somebody.soil instead of '0xa1b2C3d4Ef67aA...', or interact with 'mycontract.soil', or visit a Swarm-hosted site at 'swarmsite.soil'. will, naturally, document the heck out of it to encourage usability.

MONEY  scheduled to be delisted on May 15th at POSWallet.com
if anyone has any nodes to connect to thatd be great, ive got a couple hundred thousand MONEY on poswallet that i cant move anywhere. ive tried every node i could find on the site. ill keep my wallet open and hope we might be able to find a way to sync. with dev gone, and prices so cheap, would be a decent project to resurrect. naturally, i cant find my own node information in the debug window.

we're going to see that a lot until theres a more accepted ideal towards developers having identity verification to post [ANN]s in the first place, similar to how a dev needs to build an "enhanced identity" at bittrex in order to get their currency considered for inclusion. projects like this DO have advantages with absentee-developers. with his small premine (100.000 BIOB) there isnt much weight there to severely affect any further community commits to the project even if he hasnt sold it off already.

and truth be told, things DO happen in a devs real life... i was hospitalized thanks to insanely bad seizures for several months and was unable to contribute to my own project, SOILcoin... its taken months of work rebuilding a dev team and working to upgrade our code while trying to get relisted on exchanges and prove the serious intent of our team... unfortunately, thats not normally the case and devs that abandon ship usually just pop up under a different handle with a similar promise. (the irony of this dev mentioning that same scenario in the OP)

its a shame because this looked like it would have been a good fit for the sort of eco-crypto hub of cryptocurrencies id like to see organized, and with SOILcoin implementing SWARM in the next few weeks, to offer "serverless website hosting" sorta stuff thru the bzzz protocol, on the SOILnet. hopefully part of the community comes together with an idea to work with the direction this coin couldve gone, and id be willing to help with that.

my staked weight (22230) has finally gone above the network weight (17843)! according to the blockchain estimate, i should stake in 47 seconds. i understand a lot of people's frustrations regarding the staking with NOBT, but ive seen the same thing occuring with other projects as well, and the end of POW for those currencies is much further down the road than what is faced by this project. with NOBT approaching listing on exchanges via voting, at least ones a little more user friendly than whats available presently (as a personal preference), at least there can be some market movement of NOBT around. id hope that those whove mined it thru PoW will consider holding and staking their balances rather than simply dumping for a quick profit, with a decent APR this is a currency that can maintain a better valuation by having a slower inflation of coins in circulation. ive talked privately with the developer of NOBT a few times, and he comes across as a developer who is working to stay the course and build upon his currency to provide a more inclusive platform of services, but dealing with how the chain has reacted so far has taken a lot of his time. ive encouraged him to stay the course and keep putting in the thankless hours streamlining his presentation and building a community behind his project, crypto development is a tough job, even with ready-made cloned currencies, where a lot of those out for a quick buck dont care how it works or why, whereas "Nobtcoin" has asked a thousand questions about what can be done differently or done better, and that shows me that he's determined to stick the course on this project and make something out of it. a few weeks of patience, letting your balance collect coinage, (there is no StakeMaxAge, so you are still building your stake interest) in the grand scheme of things, isnt too bad an issue. my wallet still shows 23 active connections, so this coin is healthy, it just needs, like any balance... a little time to mature.

hopefully the final day of simply documenting the improvements and adjustments to the SOILnet taking effect with our scheduled hard forks in the new gsoil client release....

*gsoil will include a built-in netstats reporter with the ability to register a user node on the service simply thru the console. The ultimate goal would be to have the SOILcoin network intelligence tool return its report via a swarm-hosted page on the SOILnet, presently we will be able to take advantage of the service offered by miners-zone in correlation to their SOILcoin mining pool accessible at http://soil.miners-zone.net:9090/.  

Usage:

In case we had not covered this information previously, this page presents an overview of the current state of the SOILcoin blockchain. Although it is generally self-explanatory, for the sake of novices attending the page for the first time, the items represented are:
And below you see details of nodes connected to the network stats page you are viewing.

*WHISPER : with implementation the second scheduled fork in the new gsoil client, the Whisper V5 protocols will be more enabled on teh SOILcoin blockchain. The Whisper Mail server package will be included in the go-soil distributions under cmd/wnode/main.go. While a full on user-manual will hopefully be prepared for SOILcoin before this fork takes place, this is at least a good time to bring up what Whisper means to the evolution of the SOILnet in general.

Whisper is designed to run as a built-in, network-level identity-based on-chain messaging system, peer-to-peer or contract-to-contract; using the underlying devp2p Wire Protocol. It is designed for simple and efficient message broadcasting, and for asynchronous communications. Using Whisper with the most secure options, this protocol can theoretically deliver "full darkness" to messaging, that  is pure anonymity regarding sender, location, etc. This level of privacy is set to be configurable.

All Whisper messages are encrypted, then sent via the devp2p protocol, which in turn uses its own encryption on top of Whisper encryption. These are placed in Envelopers, which contain the encrypted payload and some metadata in plaintext format necessary for the decryption. Envelopes are transmitted as RLP-encoded structures of the following format:

[ Version, Expiry, TTL, Topic, AESNonce, Data, EnvNonce ]


Messages can be decrypted by anyone who possesses the corresponding key. Every Whisper node may possess multiple symmetric and asymmetric keys, and upon Envelope receipt, the node will attempt to decrypt it with each of the keys, depending on Envelope's encryption mode. In the case of successful decryption, the plain message is passed to the corresponding dApp.

Whisper nodes have zero knowledge regarding the contents of Envelopes to which they cannot decrypt. Whisper nodes simply pass Envelopes around regardless of their ability to decrypt the message.

The purpose of PoW within the Whisper protocol is to prevent spam, which can be used as a DDOS attack vector; but also serves to reduce  the computational burden of Whisper interactions on the network. The cost of Whisper PoW can be regarded as the price paid for allocated resources if  the network is to store an Envelope for a specific time (TTL).  PoW for Whisper is designed to  be proportional to both message size and TTL.

In the current versioning of Whisper, PoW is defined as average number of iterations, required to find the current BestBit (the number of leading zero bits in the hash), divided by message size and TTL:

PoW = (2^BestBit) / (size * TTL)

Composing an Envelope from a basic payload, is designed to be accomplished in a few steps:

1.Compose the Envelope data (concatenating the relevant flag byte, padding, payload (randomly generated or provided by user), and an optional signature)
2.Encrypt the data symmetrically or asymmetrically.
3.Add a Topic.
4.Set the Time To Live attribute.
5.Set the expiry as the present Unix time plus TTL.
6.Set the nonce which provides the best PoW.

Expired messages cannot be resent via the normal Whisper channels, as they will be rejected and the peer punished. Thus, a Mail Server can be run, which would store all the messages, and resend them at the request of the known nodes through peer-to-peer communication with the node. The Mail Server can resend the expired messages directly to the recipient node, consuming the messages and no longer forwarding them any further along.

**we have a decent amount of time before both SWARM and WHISPER are fully integrated onto the SOILnet, and i will be certain to work with these two new cornerstones to our functionality to make them as user friendly and understandable as possible as they roll out into the main code as scheduled in the newest gsoil release. these are major milestones in the codebase for SOILcoin, and help us to really begin looking at the next generation dApps and content providing that will be available via the SOILcoin network.

there are only a few other releases worth of feature additions and adjustments to really document regarding these scheduled forks, hopefully i can finish this today and try to finish up what id started writing over the last week regarding Casper vs Ouroboros and the future of Proof of Stake on SOILcoin.

further documentation of changes to the underlying SOILcoin protocols and Go-OS initialized by the upcoming hard forks, bringing our code base to near congruence with Ethereum's operational ability:

via the 1.5.0 release of go-ethereum:

*Changes to the RPC API*

The behavior of eth_sign is changed. It now accepts an arbitrary message, prepends a known message ["\x19Ethereum Signed Message:\n" + len(message)], hashes the result using keccak256, and then calculates the signature of the hash (breaking backwards compatibility). By adding a prefix to the message, this makes the calculated signature recognizable as an Ethereum-ecosystem specific signature. This prevents misuse where a malicious DApp can sign arbitrary data (e.g. transaction) and use the signature to impersonate the victim.

Added RPC calls related to this function include personal_sign, which functions similarly to eth_sign but also accepts a password; and personal_recover, which returns the address of the account that created the signature.

usage:
personal_recover(message, signature)
personal_sign(hash, address [, password])

Further, other added RPC functions are:
personal_importRawKey : import an unencrypted private key via RPC.
eth_getRawTransaction : returns the RLP encoding of a transaction.

debug_traceTransaction : run a transaction via debugging in the exact same manner as it was executed on the network. Alongside the  transaction hash, optional secondary arguments can be specified:

disableStorage: BOOL. Setting this to true will disable storage capture (default = false).
disableMemory: BOOL. Setting this to true will disable memory capture (default = false).
disableStack: BOOL. Setting this to true will disable stack capture (default = false).
fullStorage: BOOL. Setting this to true will return you, for each opcode, the full storage. This is a slow process. (default = false)

tracer: STRING. Setting this will enable JavaScript-based transaction tracing. If set, the previous four options will be ignored. JavaScript-based tracing enables the user to evaluate an object with (at least) two methods, named step and result. Step is a function that takes two arguments, log and db, which are called for each step of the EVM, as the specified transaction is traced.

The log contains the following fields:

pc: Number, the current program counter
op: Object, an OpCode object representing the current opcode
gas: Number, the amount of gas remaining
gasPrice: Number, the cost in wei of each unit of gas
memory: Object, a structure representing the contract's memory space
stack: array[big.Int], the EVM execution stack
depth: The execution depth
account: The address of the account executing the current operation
err: If an error occured, information about the error

db has the following methods:

getBalance(address) - returns a big.Int with the specified account's balance
getNonce(address) - returns a Number with the specified account's nonce
getCode(address) - returns a byte slice with the code for the specified account
getState(address, hash) - returns the state value for the specified account and the specified hash
exists(address) - returns true if the specified address exists

timeout: STRING. Overrides the default timeout of 5 seconds for JavaScript-based tracing calls. Optional string values are discussed at length in the go language documentation at https://golang.org/pkg/time/#ParseDuration

USAGE:
Go:            debug.TraceTransaction(txHash common.Hash, logger *vm.LogConfig) (*ExecutionResurt, error)
Console:    debug.traceTransaction(txHash, [options])
RPC:        {"method": "debug_traceTransaction", "params": [txHash, {}]}

Features added into the 1.5.0 (Let There Be Light) release, but flagged as "experimental" but show the sorts of functions that are being added into the performance of the SOILnet EVM which will allow us to build bigger and better applications going forward. Naturally we will maintain observation of code-releases from Ethereum Core, and when these features are stablized we will document them further, but as of yet, I havent had the chance to test them on the SOILnet, it is simply nice to know that these attributes are becoming available. Typical caeat... use these features at your own risk.

*gsoil will be enabled to run in Light Client mode with the --light flag. Light client mode syncs recent block headers and fetches state values on demand. NOTE: light client servers will need to be first made available. Users can set up as a light-client server using the --lightserv flag. A light server is a full node with "LES server" option enabled. i.e:

allocates 25% of CPU power towards providing a Light Client Server

The purpose of the Light Ethereum Subprotocol (LES) protocol is to allow users in low-capacity environments (embedded "smart property" environments [eg: an object which hosts an externally-owned account or a contract account], IoT enabled devices, smartphones, browser extensions, older desktop computers and laptops, etc) to maintain high-security assurances regarding the current state of user-defined part of the SOILnet state or to verify the execution of transactions and smart contract operations. Light Clients do not run a full node, but can receive data from the network.

Light Clients will be able to perform many operations: requests regarding the state of an account (nonce, balance, code or storage index), requests regarding transaction confirmations (within  consumer-merchant scenarios), request block validations or set to watch for and log blockchain events, which is useful where a dApp needs to keep track of certain events that are nt part of the permanent state of the platform but need to be verifiable in an efficient manner, such as a decentralized exchange logging trades or internal wallet transactions.

Light Clients will also make cross-chain inter-operability much more feasible. As SOILcoin maintains a Bitcoin Light Client in the operation of the BTCrelay application, which allows a SOILnet resident smart contract to request verification of transactions occuring on the BTC blockchain to enable state changes (value transactions) on the SOILcoin blockchain, a SOILcoin Light Client may make it easier for other currencies to also build relays to SOILcoin, especially alt-etherea Dagger based currencies.

There are limitations to what the light client can do presently. The only pending transactions a light client knows about are the ones that have been created and sent from that client. Likewise, locally created transactions can only be found by searching for it's hash.  Finding other transactions is a bit trickier. Searching for events (transactions) in a long blockchain history will take an extremely long timeas searches are only performed in individual headers, rather than using a MIP-mapped filter as full clients use to search, in a faster and cheaper manner.

The advantages of Light Clients is that they take up far less disk space to maintain their database, allowing it the ability to sync in minutes, but nonetheless fully interacts with the SOILcoin blockchain, and is usable through the DUST browser for SOILsafe.
 
*The Swarm daemon (bzzd) and associated helper tools are included with the latest go-soil builds and are somewhat functional. SWARM is the EVM protocol designed for decentralized file storage. The release included with go-soil is considered a Proof-of-Concept implementation of the Swarm protocol. It is included as a separate daemon process (and inherently executable binary), not embedded inside gsoil.

The objective of Swarm is to provide a decentralized store of and distribution channel for dApp code and data as well as other user defined data. Participants will be able to efficiently pool storage and bandwidth resources to provide these as services to other participants as an on-chain P2P data-storage and data-serving protocol that is DDOS-resistant, and which thanks to the underlying SOILcoin blockchain, maintains "zero-downtime" (data delivery would be based upon average block times),  and is designed to be self-sustaining with a built-in incentivization system which leverages p2p accounting, permitting the exchange of resources (storage space, bandwidth) for payment.

Swarm will, as a native base layer of the SOILcoin web three stack, continue to evolve its services and implementations, and dApps are already appearing to leverage this technology: album - a photo album dapp with a set of public-domain photographs that lets users upload their own photos; and filemanager - a GUI explorer for file collections hosted on the swarm.

Swarm is designed to deeply integrate with the devp2p multiprotocol network layer of SOILcoin, as an alt-etherea currency, as well as with the SOILcoin blockchain for application services (domain name registration, payments for services, etc). Naturally, as this is rolled onto the SOILcoin network and tested, we will endeavor to provide much more in-depth documentation regarding its usage, and how to set up Swarm clients for both sides of the economic model, as well as ensure swarm-dApps a

Ive followed the Swarm project as it has moved towards implementation within go-ethereum, and this will be one of the projects getting a lot of my attention over the next few months as its integration onto the network layer of SOILcoin becomes hardcoded. The project is running smoothly on the Ethereum blockchain, and is actually hosting its own homepage, at:
http://swarm-gateways.net/bzz:/1b5d887cea699d18560ae6dcaf06676f5064f630978b8031d9beb6fbddd82a82

SWARM was touted as one of the three cornerstones to the EVM, and as you can see, can also be used to deliver a decentralized web via serverless content hosting, with support for browsing directly integrated within the DUST wallet for SOILsafe when we follow ETH into Metropolis. There is a TON of documentation for swarm, and thatll definitely have to be another day.

*Whisper v5 PoC code is included in the repository, but not enabled yet. Whisper protocols will enable not only users to communicate with each other, but for contracts to communicate with other contracts. Whisper is considered the third cornerstone to a decentralized internet, and has many use cases: a decentralized exchange dApp may use Whisper to broadcast an offer to sell an asset at a specific rate, and could advertise this for a set amount of time, from several minutes minutes to days. Some dAppswill require signals from eachother in order to ultimately collaborate on a transaction. Whisper can be used to build chat-rooms, or to provide "dark communications" between two parties that have no knowledge of eachother beyond a hash, with source and destination hidden from both parties, and may also leverage Swarm for file transfers initiated from Whisper chats.

As with Swarm, there is a ton of documentation for the usage of Whisper, and as it is made more available for usage, we will endeavour to provide those sorts of guides for both Whisper and Swarm on go-soil. The Whisper overview on the Ethereum wiki is a good place to start to understand how to interact with Whisper (https://github.com/ethereum/wiki/wiki/Whisper-Overview) but we'll try to include this sort of information when Whisper implementation is fully realized.

*go-ethereum is able to be used as a library in Android (Java) and iOS (ObjC/Swift) projects with the 1.5.0 code release. abigen, discussed in a previous post, has gained preliminary support for creating Java bindings to EVM-level smart contracts. this may make running full node or light clients on Android and iOS devices much more attainable, and again, opens up interactivity for building projects such as the DUST wallet for SOILsafe on a smart phone, allowing for dApp interaction, file storage and service thru Swarm or anonymous messaging thru Whisper.

essentially a lot of the changes reflected in the newer code changes to Ethereum which we are upgrading SOILcoin to are providing the architecture needed to begin building those sorts of distributed applications for the industries we indentified as underserved and most likely to benefit from the sort of decentralized services our blockchain will be able to offer at a exponentially smaller cost than current models of cloud service delivery, or virtual hosting needs.

capitalizing on these advantages over the next few years will be what sets SOILcoin aside from other projects, and these evolutionary adjustments to what we can offer brings the IDEA of what the SOILnet can offer more than a few steps closer. theres a lot of work to be done, but every step made makes the SOILnet that much more accessible and readily available, even to users who wont even realize they are interacting with it (decentralized webpages), which is the ultimate idea behind a decentralized web.

more to come, as ETH wasnt done improving their codebase, and those changes reflect to how the SOILnet operates, and what it is capable of. honestly, the tools we are making available EXCITE me, almost as much as when hearing about Ethereum for the first time somewhere near two years ago and getting involved on their test-net. this project has for a long time been about the possibilities of what we will be able to create and offer, and i knew early on that it would take time for the underlying infrastructure to catch up with the ideas that were floating around my brain. we're getting there now, we're approaching that point where EVERYTHING changes, where this technology finally disrupts every industry, and with SOILcoin focused on delivering applications that will ultimately serve to make this planet not only more efficient, but healthier and greener, we stand on the precipice of an age where every one of us can make a difference, where true collaboration without censorship can be achieved.

ive always been a somewhat utopian thinker, and realized early that blockchain technology.. extraspecially the EVM.. was going to be the game changer that alters society, and that adoption of these sorts of technology is a very exponential curve, we're still... 18 months after the genesis of the SOILnet... at the base of this curve, and we're still alive and... well... BLOCKING. i think we are better prepared to ride this wave than a lot of other alt-etheria, more so because i believe we have a better vision towards the scale of how big this can get, in a practical sense. hopefully with these sorts of changes, we can position ourselves to make some noise in the crypto world finally....

ive been staking CHESS on my desktop for a few weeks and it performs wonderfully, no hiccups at all. it has a lot LESS "Generated but not accepted" blocks in my transaction history than most other currencies I actively stake. generally over 15 active connections, a decent netstakeweight, with 50k CHESS ive staked nearly 1k in two weeks, so it seems to be running exactly as advertised....

i was actually looking over my wallets this morning thinking about which ones to abandon and sell off, with the idea of increasing my balance of CHESS, before the price goes up too much more. theres few coins i hold long term, maybe a dozen active wallets running on my system, and CHESS is swiftly becoming one of the staples there,

i play chess every day, on facebook, albeit not very well, really..... but i have also made some of my most enduring friendships over the chessboard during the years. its my brain-reset exercise after dealing with development of my own crypto project. that being said, id love to see a tourney set up on some chess server with CHESS as the prizes. that might be one way to start introducing it to the chess playing community.

updates to the go-soil protocols thru the upcoming hard fork that will bring us to near-congruency with the codebase offered thru ETH. (documenting upstream from changes introduced via go-ethereum 1.4.11 (Minor Text Fixes) thru

A new build script, ci.go, was released to replace some of the older shell scripts, and can compile go-soil, run the tests and create release archives as well as debian source packages. The ci command is named from "Continuous Integration" scripts. The idea put forth is for Ubuntu packages is to run ci.go alongside the buildbot-based PPA uploads. This is meant to streamline build processes of different code changes to the core system, both soft and hard fork types.

Usage:

the available commands are:
 install    [ packages... ]                                  -- builds packages and executables
 test       [ -coverage ] [ -vet ] [ packages... ]   -- runs the tests
 archive    [ -type zip|tar ]                               -- archives build artefacts
 importkeys                                                    -- imports signing keys from env
 debsrc     [ -sign key-id ] [ -upload dest ]        -- creates a debian source package

Several security fixes were set up, generally in response to different DOS attacks that Ethereum, and other Dagger parallel currencies experienced at the time, generally finding that certain opcodes that read the state tree were under-priced in gas costs relative to other opcodes. These were used with recursive attack vectors to degrade network performance via transaction spam. Gas costs were significantly raised for EXTCODESIZE, EXTCODECOPY, CALL, CALLDELEGATE, CALLCODE which makes DOS attacks geared towards system computational degradation through "transaction spam" generally more costly than would be worth the possible damage. Replay attack protection was instituted to prevent transactions from a forked chain (eg ETH forked from ETC) being considered as legitimate on the other chain by introducing a CHAIN_ID variable.

this may come in handy later when cross-chain alt-etherea such as SOIL, ETC, UBQ et al can freely communicate, either directly or via bridged smart contracts, with assets identified by their host CHAIN_ID.

Contract code has also been placed with a size limit to assist in defending against "transaction spam" attacks. The solution decided upon was to put a hard cap on the size of an object (contract code file) that can be saved to the blockchain, in a non-disruptive way. The size cap is set at a value slightly higher than what is feasible with current gas limits (a worst-case scenario sort of contract can be created with ~23200 bytes using the 4.7 million gas/block limit, whereas a normally created contract can go up to ~18 kb).

Ill finish up withthe update documentations tomorrow... theres a hockey game on. Some things take precedence. Have a great night...............

further protocol and blockchain upgrades via updates from 1.4.1 (Knoxjonesi) thru 1.4.7 (Colourise) implementations on SOILcoin:

The  --genesis <json_file> flag used with private chains has been deprecated and replaced with the sub-command geth init <json file> to prevent the use of the --genesis flag with other flags, which was causing problems. A new field added to the genesis file: config allows the specification of configuration options for the use of private chains. *At present the only available option is "homesteadBlock":"0x block_number"*  

ADDED DEBUGGING OPTIONS:

traceTransaction( hash )
traceBlockByHash( hash )
traceBlockByNumber( number )
traceBlockByFile( file_with_rlp_encoded_block )
traceBlock( rlp_hex_encoded_string )

* accessed through either HTTP, IPC, or WebSocket RPC and the geth console.

minor fixes in 1.4.5 included some bug fixes related to WebSocket HTTP origins, and stopping transaction handling during the initial fast sync of a client to speed up the process. also introduced is a new RPC method: PrivateAccountAPI.SignAndSendTransaction which accepts a transaction and password as arguments. This allows external applications to submit transactions without the need to first unlock an account, which presented a potential attack vector during the small time window a wallet is unlocked, in order to submit a fraudulent transaction.

*EDGE*, or Enhanced Data Rates for GSM Evolution, introduces improved blockchain download concurrency to avoid bottlenecks caused by remote machines with poor connections, as well as an adaptive "quality-of-service tuning" allowing peer selection to be less aggressive for users with more restricted connectivity. The result is an improved blockchain syncing mechanism that can produce up to 8MB/s download speeds to retrieve the SOILcoin network blockchain (if your connectivity allows it), and provides a solid and stable stream for all users, verified for as low as EDGE connections (440ms latency, 200 kbps upstream, 220kbps downstream).

Blockchain syncing is further improved via concurrent downloading of block headers from several peers compared to the previous single-peer header-download which uses it's peers to download the block bodies, receipts, state, etc that the header chain defined. Now, using the concept of a "header skeleton" wherein a single "master-peer" is used to retrieve a skeleton of the header chain: where only every Nth header is retrieved, forming gaps of N-1 headers. Simultaneously, all the master's peers are used to fill in the missing N-1 headers, creating a batching solution and speedier blockchain sync.

((i timed the SOILcoin blockchain download for resyncing to the new client at a little over 12 minutes on the DUST client for SOILsafe. i can attest to nearly 24 hours of time downloading the blockchain with the previous version, and this change also scales the technology further towards being able to provide a Light SOIL Client, which again has its own advantages...))

The command exec.LookPath(solcPath) has been added to go-soil, which corrects issues in locating solc.exe for the development environment compiling of Solidity contracts. The JavaScript console was also cleaned up, and moved to its own package in the go-soil build, which will make it easier to make use of the console in dApps and other projects that embed gsoil into their own processes.

simply working our way forward through the updates is likely the easiest way to describe the changes forthcoming on the SOILnet. ill deal with these changes one or two aspect per post, and try to make it as understandable as possible.

Go 1.4.1 (Knoxjonesi) introduces

*Event Subscriptions*, or RPC PUB SUB, wherein an active, connected node can subscribe to blockchain event notifications rather than manually requesting them directly. the node will create a subscription id and provide notifications via RPC as subscription events occur. these subscriptions can be cancelled thru calls or by closing the connection to the gsoil client. these subscriptions are coupled to your connection to the SOIL network, thus if the connection is terminated, all subscriptions are automatically closed

example: creating a subscription
Subscriptions are created via a regular RPC call with eth_subscribe as method and the subscription name as the parameter. If successful it returns the subscription id (your active wallet address).


produces subscribed results to the determined address (0xcd0c3e8af590364c09d0fa6a1210faf5) when new blocks are set on the blockchain.


and can be unsubscribed to by

currently supported subscriptions are (ie: placed in stead on "newBlocks" in the above example):
newHeads - produces a notification with new block header information, including difficulty, gas limit, miner, nonce, timestamp, etc.
logs - returns logs that are included in new imported blocks and match the given filter criteria, ex: addresses (personal or contract) or arrays of addresses, or topics. only logs that are created from events matching these filters are returned
newPendingTransactions - returns the hash for all transactions that are added to the pending blockchain state
syncing - a boolean return to provide notices of block chain synchronization start/stops

future available subscriptions being worked upon beyond this implementation will also provide subscription notices for current events related to balance changes, account changes, nonce changes and storage changes in contracts.



*Native Go DApp Development*, introduces a new tool called abigen (located in cmd/abigen) which enables fully automated creation of Go Bindings to any contract built for deployment on the SOILnet. In order to ensure client implementation for applications in various programming languages that operate on the EVM, and allowing for a streamlined approach to mainstream adoption, RPC interfaces for JavaScript dApps have made it possible for most use cases where manual interaction with the blockchain is necessary. The server side RPC use cases, where other languages are used (i.e.: backend data-access layers written in NodeJs, Python, Ruby or Perl; database administration; security and authentication) these bindings have been elusive.

abigen allows for work on server side native dApps, ensuring that Go-language bindings to contracts on the SOILnet are safe at the time of compiling and deployment, and that they can be independently, automatically and completely generated from a contract ABI or EVM bytecode. Overall, abigen will make it exponentially easier to construct functioning contracts on the SOILnet that are interactive within the DUST brower for SOILsafe.

The available tutorial for ETH regarding abigen relates to using the "official Token contract" (token.sol) as the base for introducing the Go native bindings. This contract source code repo is available at: https://gist.github.com/karalabe/08f4b780e01c8452d989 and is the ETH foundations representation as the common form of creating a token for oneself. (which can be done directly from within the DUST wallet for SOILsafe).

Interacting with a contract on the SOILcoin blockchain directly from the Go client (gsoil) is already possible via the RPC interfaces exposed by the client. Writing the boilerplate code that translates Go language constructs into RPC calls and back requires a lot of code to perform minimal functions, and as an aspect of application development... is an excessive time consumer and even small changes in Solidity can require a great deal of work to disposition the code to Go. With the introduction of abigen, the SOILcoin implementation of go-ethereum (go-soil) has a source code generator that will convert SOILcoin ABI definitions into ready-made Go packages. Assuming a valid Go development environment is set up, with godep installed, and an up-to-date build of gsoil, you can build the Go binding Generator with:


GENERATING BINDINGS: The one prerequisite needed to generate a Go binding to an SOILcoin contract is that contract's ABI definition JSON file. For the example Token contract this is obtained by either compiling the Solidity code yourself (via an online solidity compiler such as at https://ethereum.github.io/browser-solidity/#version=soljson-v0.4.11+commit.68ef5810.js or https://etherchain.org/solc), or by using a  pre-compiled token.abi available at https://gist.github.com/karalabe/b8dfdb6d301660f56c1b.

To generate a binding, call:


The flags are:
--abi: (Mandatory) path to the contract ABI to bind to
--pgk: (Mandatory) Go package name to place the Go code into
--type: (Optional) Go type name to assign to the binding struct
--out: (Optional) output path for the generated Go source file (not set = stdout)

This will generate a type-safe Go binding for the Token contract. The generated code will look something like token.go as referrenced by the original tutorial for this update, (https://gist.github.com/karalabe/5839509295afa4f7e2215bc4116c7a8f), but as the generator itself is upgraded, the structure of the Go bindings may change, and it is recommended to generate the bindings fresh when preparing to deploy this contract (token.sol) on the SOILcoin network.

The Go binding generator also produces ready-built RPC backends which can be attached to an active SOILcoin node via IPC, HTTP or WebSockets, and through which the user can access the SOILcoin network and further connect to, interact, and perform transactions with contracts deployed on the SOILnet. The generator also creates specialized wrappers which can be pre-configured with authorization parameters, allowing all the Solidity defined methods to be called by simple session commands.

Deploying contracts onto the SOILnet using abigen requires the use of the contract bytecode alongside the contract ABI. This is retrieved via the previously mentioned online compilers, where the token.sol contract code can be compiled, generating the bytecode (similar to the presented example from the original tutorial, found at https://gist.github.com/karalabe/026548f6a5f5f97b54de) saved as token.bin


This will generate something similar to the above referenced token.go with the addition of a DeployToken function.

abigen also allows for Go binding directly from Solidity source code, which first compiles the source code (via --solc) into it's fundamental commands and functions and binds using that. This has the added function that all contracts contained within a given Solidity source file are built and bound, so if the file contains many contract sources, they will all be available from Go code.


Much of the Go binding generation process can be automated during contract updating by leveraging the go:generate binding into a Go source file before the package definition, after which whenever the Solidity contract is modified, instead of needing run the above command, a call go generate on the package will correctly generate the new bindings.


The final update that abigen presents is a very useful one, which i think may open up a great deal of possibilities for on-chain token economies going forward.  A simulated blockchain can be built as a backend to native contracts the same way as a live RPC backend could be, and which can be "mined" thru calling Commit. the adjusted code presented in the original tutorial for abigen follows:


The original tutorial regarding abigen has a number of examples for usage, and when time permits, I'll write a tutorial showing how to use abigen via a gsoil development set-up, connecting to a similar sort of token on SOIL that the tutorial points towards (the Ethereum testnet Unicorn which mints 1 UNICORN to an address for every 2.something ETH sent to the contract address) and will add that information to this post when we set it up on the SOILcoin forum (which in and of itself still needs to be set up, just havent had the hours available to commit to that project yet.)