Pages:
Author

Topic: [ANN][$MUSIC] Musicoin Blockchain Upgrades to V3.0(“Quantitative Tightening 🎸 - page 96. (Read 287558 times)

full member
Activity: 675
Merit: 100
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?

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.
full member
Activity: 298
Merit: 100
New desktop wallet (v0.6)  with $MUSIC 2.0 will be released next week. Please stay tuned.

 

Release note:  (please upgrade your client asap)

GMC client with UBI Scheme (V2.0.0)


https://github.com/Musicoin/go-musicoin/releases

UBI scheme is implemented in this release. A hardfork of $MUSIC blockchain will be triggered at block 1,200,000 automatically without manual interference.

Old version of clients(<2.0.0) are not compatible with this release. All miners and desktop wallets should update to this version to sync with the whole network including all exchanges.

Several other security issues have been fixed in this release as well.

Note: Some Parity-based clients will not work with this version of client until we have some further notice!!!



sorry im new to this, do i just download the file named: gmc-windows-4.0-amd64.exe and run it? when i do i get  a cmd prompt and it shows its going through blocks 1 imported 30 imported etc...
fyi im running windows 10 64bit.
full member
Activity: 298
Merit: 100
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?

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.
full member
Activity: 675
Merit: 100
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?
full member
Activity: 298
Merit: 100
The price is popping in the last few hours, what is going on?  Someone pumping it?

nope, i wouldn't call that a pump, the last freakin pump had over 1000 btc in 24 hours. right now it's only up 20 btc. i expect it to drop the closer we get to fork time since everyone will be yanking.

edit: it shot up 100 btc in a few hours...... could be the fork update and all the stuff thats coming.
full member
Activity: 675
Merit: 100
The price is popping in the last few hours, what is going on?  Someone pumping it?
sr. member
Activity: 512
Merit: 260
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
sr. member
Activity: 512
Merit: 260
Thank you for the info, but not having fun. Tryed a few things but not working

ubuntu@ip-172-31-34-201:~$ export GOROOT=/home/ubuntu/go                       
ubuntu@ip-172-31-34-201:~$ export PATH=$PATH:$GOROOT/bin
ubuntu@ip-172-31-34-201:~$ go version
go version go1.6.3 linux/amd64


sudo nano ~/.profile

# set PATH so it includes user's private bin directories
PATH="$HOME./home/ubuntu/go/bin:$HOME/bin:$HOME/.local/bin:$PATH"


$ go version
go version go1.6.3 linux/amd64

:-(

you have at least two go binaries in your PATH variable. you have to get rid of the old one.

try these 4 steps:

1. $ which go
===== the output will show you the "old" go binary. copy the whole string
example:
orchard@ethereum-1:~$ which go
/home/orchard/go/bin/go

2. $ mv
===== where copiedstring is the output of #1. this will rename the "old" go to go.old
example:
mv /home/orchard/go/bin/go /home/orchard/go/bin/go.old

3. $ which go
===== at this point, the new go should appear
i.e.  /home/ubuntu/go/bin/go

4. $ go version
===== hopefully new version should be displayed.
go version go1.7.3 linux/amd64



If i do this i get a message that no golang is installed

something this simple is stopping me dead.
full member
Activity: 420
Merit: 101
Thank you for the info, but not having fun. Tryed a few things but not working

ubuntu@ip-172-31-34-201:~$ export GOROOT=/home/ubuntu/go                       
ubuntu@ip-172-31-34-201:~$ export PATH=$PATH:$GOROOT/bin
ubuntu@ip-172-31-34-201:~$ go version
go version go1.6.3 linux/amd64


sudo nano ~/.profile

# set PATH so it includes user's private bin directories
PATH="$HOME./home/ubuntu/go/bin:$HOME/bin:$HOME/.local/bin:$PATH"


$ go version
go version go1.6.3 linux/amd64

:-(

you have at least two go binaries in your PATH variable. you have to get rid of the old one.

try these 4 steps:

1. $ which go
===== the output will show you the "old" go binary. copy the whole string
example:
orchard@ethereum-1:~$ which go
/home/orchard/go/bin/go

2. $ mv
===== where copiedstring is the output of #1. this will rename the "old" go to go.old
example:
mv /home/orchard/go/bin/go /home/orchard/go/bin/go.old

3. $ which go
===== at this point, the new go should appear
i.e.  /home/ubuntu/go/bin/go

4. $ go version
===== hopefully new version should be displayed.
go version go1.7.3 linux/amd64

sr. member
Activity: 512
Merit: 260
Thank you for the info, but not having fun. Tryed a few things but not working

ubuntu@ip-172-31-34-201:~$ export GOROOT=/home/ubuntu/go                       
ubuntu@ip-172-31-34-201:~$ export PATH=$PATH:$GOROOT/bin
ubuntu@ip-172-31-34-201:~$ go version
go version go1.6.3 linux/amd64


sudo nano ~/.profile

# set PATH so it includes user's private bin directories
PATH="$HOME./home/ubuntu/go/bin:$HOME/bin:$HOME/.local/bin:$PATH"


$ go version
go version go1.6.3 linux/amd64

:-(




full member
Activity: 420
Merit: 101
So I followed this guide https://golang.org/doc/install/source but no success.

here is the commands.

$ git clone https://go.googlesource.com/go
$ cd go
$ git checkout go1.7.3
$ git checkout master
$ cd src
$ ./all.bash

ubuntu@ip-172-31-34-201:~/go/src$ ./all.bash
##### Building Go bootstrap tool.
cmd/dist

##### Building Go toolchain using /usr/lib/go-1.6.
....

## Testing packages.
....

ALL TESTS PASSED

---
Installed Go for linux/amd64 in /home/ubuntu/go
Installed commands in /home/ubuntu/go/bin
*** You need to add /home/ubuntu/go/bin to your PATH.


$ go env
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH=""
GORACE=""
GOROOT="/usr/lib/go-1.6"
GOTOOLDIR="/usr/lib/go-1.6/pkg/tool/linux_amd64"
GO15VENDOREXPERIMENT="1"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0"
CXX="g++"
CGO_ENABLED="1"


I have restarted the terminal but I still get

$ go version
go version go1.6.3 linux/amd64






"*** You need to add /home/ubuntu/go/bin to your PATH."

Your environment variable PATH is still pointing to the old go binary.

Try the command "which go" to see its current path.

You need to make sure go is pointing to the new path by creating a softlink to the new binary or by readjusting PATH.
sr. member
Activity: 512
Merit: 260
So I followed this guide https://golang.org/doc/install/source but no success.

here is the commands.

$ git clone https://go.googlesource.com/go
$ cd go
$ git checkout go1.7.3
$ git checkout master
$ cd src
$ ./all.bash

ubuntu@ip-172-31-34-201:~/go/src$ ./all.bash
##### Building Go bootstrap tool.
cmd/dist

##### Building Go toolchain using /usr/lib/go-1.6.
....

## Testing packages.
....

ALL TESTS PASSED

---
Installed Go for linux/amd64 in /home/ubuntu/go
Installed commands in /home/ubuntu/go/bin
*** You need to add /home/ubuntu/go/bin to your PATH.


$ go env
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH=""
GORACE=""
GOROOT="/usr/lib/go-1.6"
GOTOOLDIR="/usr/lib/go-1.6/pkg/tool/linux_amd64"
GO15VENDOREXPERIMENT="1"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0"
CXX="g++"
CGO_ENABLED="1"


I have restarted the terminal but I still get

$ go version
go version go1.6.3 linux/amd64




sr. member
Activity: 512
Merit: 260
I am trying to run a  full node on an AWS ubuntu 16.0.4

as it has an old go installed I want to updated the golang.


I can't seem to do this step

"Install the latest distribution of Golang (v1.7) "

running Ubuntu 16.04


$ sudo apt-get install bison mercurial bash < <(curl -LSs 'https://raw.githubusercontent.com/moovweb/gvm/master/binscripts/gvm-installer')

$ . "$HOME/.gvm/scripts/gvm"

$ gvm version
Go Version Manager v1.0.22 installed at /home/myuser/.gvm

$ gvm listall

gvm gos (available)

   go1
   go1.0.1
   go1.0.2
   go1.0.3
   go1.1
   go1.1.1
....

$ gvm install go1.7.3
Installing go1.7.3...
 * Compiling...
ERROR: Failed to compile. Check the logs at /home/ubuntu/.gvm/logs/go-go1.7.3-compile.log
ERROR: Failed to use installed version

$ cd /home/ubuntu/.gvm/logs/
$ tail -n 100 go-go1.7.3-compile.log
##### Building Go bootstrap tool.
cmd/dist
ERROR: Cannot find /home/ubuntu/go1.4/bin/go.
Set $GOROOT_BOOTSTRAP to a working Go tree >= Go 1.4.

$ go version
go version go1.6.3 linux/amd64


member
Activity: 137
Merit: 10
New desktop wallet (v0.6)  with $MUSIC 2.0 will be released next week. Please stay tuned.

 

Release note:  (please upgrade your client asap)

GMC client with UBI Scheme (V2.0.0)


https://github.com/Musicoin/go-musicoin/releases

UBI scheme is implemented in this release. A hardfork of $MUSIC blockchain will be triggered at block 1,200,000 automatically without manual interference.

Old version of clients(<2.0.0) are not compatible with this release. All miners and desktop wallets should update to this version to sync with the whole network including all exchanges.

Several other security issues have been fixed in this release as well.

Note: Some Parity-based clients will not work with this version of client until we have some further notice!!!


member
Activity: 137
Merit: 10
Release note:  (please upgrade your client asap)

GMC client with UBI Scheme (V2.0.0)


https://github.com/Musicoin/go-musicoin/releases

UBI scheme is implemented in this release. A hardfork of $MUSIC blockchain will be triggered at block 1,200,000 automatically without manual interference.

Old version of clients(<2.0.0) are not compatible with this release. All miners and desktop wallets should update to this version to sync with the whole network including all exchanges.

Several other security issues have been fixed in this release as well.

Note: Some Parity-based clients will not work with this version of client until we have some further notice!!!

member
Activity: 76
Merit: 10
Do I have to run a full node to mine solo? It is taking very long to download the complete chain on my AWS
Yes, it is necessary to run a full node for solo mining as well. Honestly, it won't take that long. Try again, or try under a firewall network, usually be done within 30 min. When we're testing under UBI, we sync/flush 10 times a day even.

who's using nomnom? anyone else having issues with the name ID just being 0. i have 2 machine and would love ti distinguish the different hashes and whats working, but i cant since names are always 0.
If you're referring to the person who is running nomnom, it will be Jared (aka pcmode) from musiconomi.


o noice found jarred! lolwhat i'm referring to is on the site it's suppose to show how many machines are running, and the names of each machine. right now all my machines show up as 1 machine and they're all named 0.

Oh. You'll have to talk with him about it, he runs the pool.
full member
Activity: 298
Merit: 100
full member
Activity: 298
Merit: 100
Do I have to run a full node to mine solo? It is taking very long to download the complete chain on my AWS
Yes, it is necessary to run a full node for solo mining as well. Honestly, it won't take that long. Try again, or try under a firewall network, usually be done within 30 min. When we're testing under UBI, we sync/flush 10 times a day even.

who's using nomnom? anyone else having issues with the name ID just being 0. i have 2 machine and would love ti distinguish the different hashes and whats working, but i cant since names are always 0.
If you're referring to the person who is running nomnom, it will be Jared (aka pcmode) from musiconomi.


o noice found jarred! lolwhat i'm referring to is on the site it's suppose to show how many machines are running, and the names of each machine. right now all my machines show up as 1 machine and they're all named 0.
member
Activity: 76
Merit: 10
Do I have to run a full node to mine solo? It is taking very long to download the complete chain on my AWS

Yes, it is necessary to run a full node for solo mining as well. Honestly, it won't take that long. Try again, or try under a firewall network, usually be done within 30 min. When we're testing under UBI, we sync/flush 10 times a day even.

who's using nomnom? anyone else having issues with the name ID just being 0. i have 2 machine and would love ti distinguish the different hashes and whats working, but i cant since names are always 0.

If you're referring to the person who is running nomnom, it will be Jared (aka pcmode) from musiconomi.
legendary
Activity: 1184
Merit: 1017
Pages:
Jump to: