packages contain broken links to basecoin repo

[Tectract]

such as:

github.com/tendermint/basecoin/cmd/basecoin/commands

so, it no longer compiles...

[zramsay]

see #236

[Tectract]

That ticket seems to be about updating the readme. This ticket is about fixing the actual imoprt statements in the code that refer back to the old basecoin branch. They prevent the code from compiling. Fixing the readme won't help make the code compile again.

[zramsay]

ah, true. the code has been fixed on the develop branch. Compiling should work from it (and see the new documentation in docs directory)

[Tectract]

cool. ETA on release?

[ethanfrey]

Between 11-15 of September. I will do my best to keep it. Feature freeze soon and polish and testing and Bugfixing until release On Aug 25, 2017 4:43 PM, Tectract <notifications@github.com> wrote:cool. ETA on release? —You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.

[Tectract]

should I also be running dev on the tendermint branches, or a specific release, for testing with the cosmos-sdk dev branch?

[ethanfrey]

Honestly, I would wait like 5 days to working on the dev branch. There was a super push to rename. The api is not fully stable and may break. Next week without warning. Once there is feature freeze, you can start giving feedback. Until, then, reading docs, looking at code, and commenting on what is missing is great On Aug 25, 2017 5:02 PM, Tectract <notifications@github.com> wrote:should I also be running dev on the tendermint branches, or a specific release, for testing with the cosmos-sdk dev branch? —You are receiving this because you commented.Reply to this email directly, view it on GitHub, or mute the thread.

[zramsay]

@Tectract you should be OK working off of tendermint master

[Tectract]

ok, thanks for this feedback. Can you maybe give a once-over to the standAlonePassGenerate code here:

https://github.com/enledger/standAlonePassGenerate

I just want to be sure the addresses we're displaying and the passphrases / keys being generated there should work ok, as EnergyChain addresses and keys, once we go live. Our goal was to do a test "mint" of some coins, then AppTx it to one of the addresses, then try sending it back using the privkey generated by the standAlonePassGenerate tool, as an acid test of using Tendermint to actually store the EECoin balances for people during our token launch.

[Tectract]

I can switch to some other dev tasks and give you guys a few days to stabilize the cosmos-sdk repo. I'll switch to bitcoin address generation and input tx tracking over the weekend :)

[zramsay]

is there a test we can run on that code? closing this issue as resolved

[Tectract]

here's the energychain repo as it stands, I could try compiling against dev branch now, it may compile... It's just a "counter" clone so far, I was trying to figure out how to add "mintcoin" capabilities next.

https://github.com/enledger/EnergyChain

the standAlonePassGenerate tool can be simply cloned, npm i, and node standAlonePassGenerate.js

https://github.com/enledger/standAlonePassGenerate

[Tectract]

I don't know of any real way to test it other than with a basecoin node, I guess. I'm still unclear on how to test signing the funds back, using a privkey generated by this tool. Would I spin up a non-validator node with this privkey in the config maybe, and then try sending from that node?

[ethanfrey]

Tectract, I highly suggest waiting until Monday evening.

I will add an example of how to rebrand to cosmos academy. And I will do some more clean up by then.

As to the passphrase generator. You gotta ping @mappum until he gives you info. Not about this issue at all.

Please add the issue to cosmos/cosmos-sdk-js

Hopefully he responds to that. That is about all things Javascript built on this framework. This repo is just the go code and bindings