Topic: [ANN][$MUSIC] Musicoin Blockchain Upgrades to V3.0(“Quantitative Tightening 🎸 - page 95. (Read 287572 times)
September 10, 2017, 05:40:48 PM
If I mined the coins for a purse registered at the bittrex exchange - they will come in full after the update?
September 10, 2017, 02:45:13 PM
How do I transfer the wallet data to another disk? Or create on another drive? I have little space on the SSD for data.
September 10, 2017, 09:53:45 AM
I have a question - according to whattomine Musicoin profitability is roughly 10% more than for ETH. Although they both use "ethash", where does better profitability come from? Does it mean that let's say the same GPU will have better hashrate while mining musicoin than ETH because of lower network difficulty? Or there is some other reason? thanks!
The figures take into account the mining ability as well as market price. So if difficulty in musicoin were to rise, it would affect the values. In fact, any change in difficulty, price, etc changes the values
September 10, 2017, 09:01:47 AM
I have a question - according to whattomine Musicoin profitability is roughly 10% more than for ETH. Although they both use "ethash", where does better profitability come from? Does it mean that let's say the same GPU will have better hashrate while mining musicoin than ETH because of lower network difficulty? Or there is some other reason? thanks!
September 10, 2017, 02:33:23 AM
hey dev team im running version .7 wallet, and just downloaded the client v 2.0.0 and renamed gmc-windows-4.0-amd64.exe to gmc.exe an replaced the old one in my wallet folder.
everything seems to be working and looking good i current have this after checking versions:
Version: 2.0.0-stable-d849d276
Protocol Versions: [63 62]
Network Id: 7945959
Go Version: go1.7.3
OS: windows
GOPATH=
GOROOT=/usr/local/go
again thanks to orchardcoins for helping me out!!!!!
LINKS:
client exe v2.0: https://github.com/Musicoin/go-musicoin/releases
wallet v0.7: https://github.com/Musicoin/desktop/releases
everything seems to be working and looking good i current have this after checking versions:
Version: 2.0.0-stable-d849d276
Protocol Versions: [63 62]
Network Id: 7945959
Go Version: go1.7.3
OS: windows
GOPATH=
GOROOT=/usr/local/go
again thanks to orchardcoins for helping me out!!!!!
LINKS:
client exe v2.0: https://github.com/Musicoin/go-musicoin/releases
wallet v0.7: https://github.com/Musicoin/desktop/releases
always happy to help fellow forumers!
September 10, 2017, 01:24:20 AM
Do you have market research on artists who say that this is what they want? Also, in what ways does the blockchain make this the way to go rather than a traditional payment system that's fairer? Also, I notice that your Go implementation is based on Ethereum. Is there a particular reason you are using a modified version rather than a private network? And if so, what are the features added?
September 10, 2017, 01:04:03 AM
hey dev team im running version .7 wallet, and just downloaded the client v 2.0.0 and renamed gmc-windows-4.0-amd64.exe to gmc.exe an replaced the old one in my wallet folder.
everything seems to be working and looking good i current have this after checking versions:
Version: 2.0.0-stable-d849d276
Protocol Versions: [63 62]
Network Id: 7945959
Go Version: go1.7.3
OS: windows
GOPATH=
GOROOT=/usr/local/go
again thanks to orchardcoins for helping me out!!!!!
LINKS:
client exe v2.0: https://github.com/Musicoin/go-musicoin/releases
wallet v0.7: https://github.com/Musicoin/desktop/releases
everything seems to be working and looking good i current have this after checking versions:
Version: 2.0.0-stable-d849d276
Protocol Versions: [63 62]
Network Id: 7945959
Go Version: go1.7.3
OS: windows
GOPATH=
GOROOT=/usr/local/go
again thanks to orchardcoins for helping me out!!!!!
LINKS:
client exe v2.0: https://github.com/Musicoin/go-musicoin/releases
wallet v0.7: https://github.com/Musicoin/desktop/releases
September 09, 2017, 11:54:56 PM
Great development here.
Looking forward for further details - UBI 2.0
Our pool prepared for upcoming changes.
https://mc.zet-tech.eu/#
Looking forward for further details - UBI 2.0
Our pool prepared for upcoming changes.
https://mc.zet-tech.eu/#
September 09, 2017, 11:34:56 PM
Music.OrchardCoins.com Pool now with version 2.0!
http://music.orchardcoins.com/
stratum
music.orchardcoins.com:8008
looking for more miners!
September 09, 2017, 10:48:37 PM
September 09, 2017, 07:37:15 PM
just a few tips, you can print variables like this:
echo $PATH
also, when executing commands, please read all the output and keep an eye on any error/warning.
sometimes googling those errors can help.
echo $PATH
also, when executing commands, please read all the output and keep an eye on any error/warning.
sometimes googling those errors can help.
September 09, 2017, 07:31:25 PM
so i played with the path. Made sure the new go is first
export PATH=/usr/lib/go-1.7/bin:$PATH
$ go env
warning: GOPATH set to GOROOT (/usr/lib/go-1.7) has no effect
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/usr/lib/go-1.7"
GORACE=""
GOROOT="/usr/lib/go-1.7"
GOTOOLDIR="/usr/lib/go-1.7/pkg/tool/linux_amd64"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build143187690=/tmp/go-build -gno-record-gcc-switches"
CXX="g++"
CGO_ENABLED="1"
but for some reason, it is still getting 1.6.3 when I make.
$ sudo make gmc
build/env.sh go run build/ci.go install ./cmd/gmc
>>> /usr/lib/go-1.6/bin/go install -ldflags -X main.gitCommit=d849d276a68d6f7a9b86ab9cc501f65325bfda2e -v ./cmd/gmc
Done building.
Run "build/bin/gmc" to launch musicoin.
ubuntu@ip-172-31-34-201:~/go-musicoin$ cd build/
ubuntu@ip-172-31-34-201:~/go-musicoin/build$ cd bin/
ubuntu@ip-172-31-34-201:~/go-musicoin/build/bin$ ./gmc version
GMC
Version: 2.0.0-stable-d849d276
Protocol Versions: [63 62]
Network Id: 7762959
Go Version: go1.6.3
OS: linux
GOPATH=/usr/lib/go-1.7
GOROOT=/usr/lib/go-1.7
export PATH=/usr/lib/go-1.7/bin:$PATH
$ go env
warning: GOPATH set to GOROOT (/usr/lib/go-1.7) has no effect
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/usr/lib/go-1.7"
GORACE=""
GOROOT="/usr/lib/go-1.7"
GOTOOLDIR="/usr/lib/go-1.7/pkg/tool/linux_amd64"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build143187690=/tmp/go-build -gno-record-gcc-switches"
CXX="g++"
CGO_ENABLED="1"
but for some reason, it is still getting 1.6.3 when I make.
$ sudo make gmc
build/env.sh go run build/ci.go install ./cmd/gmc
>>> /usr/lib/go-1.6/bin/go install -ldflags -X main.gitCommit=d849d276a68d6f7a9b86ab9cc501f65325bfda2e -v ./cmd/gmc
Done building.
Run "build/bin/gmc" to launch musicoin.
ubuntu@ip-172-31-34-201:~/go-musicoin$ cd build/
ubuntu@ip-172-31-34-201:~/go-musicoin/build$ cd bin/
ubuntu@ip-172-31-34-201:~/go-musicoin/build/bin$ ./gmc version
GMC
Version: 2.0.0-stable-d849d276
Protocol Versions: [63 62]
Network Id: 7762959
Go Version: go1.6.3
OS: linux
GOPATH=/usr/lib/go-1.7
GOROOT=/usr/lib/go-1.7
it seems you have GOPATH misconfigured. LIB folders are used for libraries and not binaries. based on your previous post, you probably should have used "/home/ubuntu/go"
warning: GOPATH set to GOROOT (/usr/lib/go-1.7) has no effect
here is mine. try to adjust yours accordingly.
orchard@etc-eu:~$ go env
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/orchard/go"
September 09, 2017, 06:15:13 PM
Thanks RobRoy
September 09, 2017, 04:18:13 PM
anyone run the update 2.0.0 for windows 10?
also found wallet v0.7
https://github.com/Musicoin/desktop/releases
also found wallet v0.7
https://github.com/Musicoin/desktop/releases
September 09, 2017, 04:14:09 PM
September 09, 2017, 04:11:56 PM
How do you find out the current block number?
if your using the musicoin.org wallet it tells u on the bottom, or goto whattomine
September 09, 2017, 03:53:31 PM
September 09, 2017, 03:48:50 PM
How do you find out the current block number?
September 09, 2017, 01:30:27 PM
Ah ok it's the fork announcement.
Hash power is pouring into MUSIC in the last hour, up 11% already.
About when will block 1,200,000 happen?
Hash power is pouring into MUSIC in the last hour, up 11% already.
About when will block 1,200,000 happen?
u would have to calculate that yourself, every 16 seconds or so a block is found. multiply that by how many blocks left then divide that by how many seconds in a day.
About 30.5 days from now.
yeap but also keep in mind 250 gh/s just kicked in, that speeds up things super quick! tf2 i sent u a message.
Jump to: