Pages:
Author

Topic: Re: [AXIOM] AxiomMemHash, Schnorr Sigs Implemented, APOS 3.0, AXH 2.0 Proposed - page 49. (Read 204903 times)

member
Activity: 81
Merit: 1002
It was only the wind.
I'm trying to build the wallet from source, but getting this error:


secp256k1/src/ecmult_impl.h: In function âvoid secp256k1_ecmult_odd_multiples_table_storage_var(int, secp256k1_ge_storage_t*, const secp256k1_gej_t*)â:
secp256k1/src/ecmult_impl.h:96:71: warning: invalid conversion from âvoid*â to âsecp256k1_gej_t*â [-fpermissive]
secp256k1/src/ecmult_impl.h:97:69: warning: invalid conversion from âvoid*â to âsecp256k1_ge_t*â [-fpermissive]
secp256k1/src/ecmult_impl.h:98:67: warning: invalid conversion from âvoid*â to âsecp256k1_fe_t*â [-fpermissive]
secp256k1/src/secp256k1.c: At global scope:
secp256k1/src/secp256k1.c:460:48: warning: deprecated conversion from string constant to âchar*â [-Wwrite-strings]
secp256k1/src/field_10x26_impl.h:44:13: warning: âvoid secp256k1_fe_verify(const secp256k1_fe_t*)â defined but not used [-Wunused-function]
secp256k1/src/group_impl.h:36:13: warning: âvoid secp256k1_ge_set_infinity(secp256k1_ge_t*)â defined but not used [-Wunused-function]
secp256k1/src/group_impl.h:161:13: warning: âvoid secp256k1_gej_set_xy(secp256k1_gej_t*, const secp256k1_fe_t*, const secp256k1_fe_t*)â defined but not used [-Wunused-function]
secp256k1/src/group_impl.h:227:12: warning: âint secp256k1_gej_is_valid_var(const secp256k1_gej_t*)â defined but not used [-Wunused-function]
secp256k1/src/secp256k1.c:637:1: fatal error: opening dependency file obj/secp256k1/src/secp256k1.d: No such file or directory
compilation terminated.
make: *** [obj/secp256k1/src/secp256k1.o] Error 1


Nevermind, found part of the fix on page 4, however now I get this:



/usr/local/include/boost/filesystem/operations.hpp:508: undefined reference to `boost::filesystem::detail::rename(boost::filesystem::path const&, boost::filesystem::path const&, boost::system::error_code*)'
collect2: ld returned 1 exit status
make: *** [axiomd] Error 1


I'm using boost 1.55

do you have the all the boost dev packages installed also? ...

just a shot in the dark with that question Wink ...

#crysx

Were the libs not there, it'd be bitching about a library missing - no, my best guess based on the available information is that he's simply not linking against libboost_filesystem - -lboost_filesystem should do it.
hero member
Activity: 1022
Merit: 1000
a fair bit of orphan blocks...

From POS or POW?

I have 4 orphan blocks in the last week and 68 correct blocks.

I have been finding blocks with coin clumps of 100 axiom. Quite happy with the results so far
hero member
Activity: 588
Merit: 501
does anyone know how to setup the QT for solo mining? i have tried adding a .conf file with a user and password to connect with, and -server=1 is there. but still no luck connecting the nicehash miner to my wallet

Won't work.. Nicehash requires stratum, the wallet is getwork.

sorry shouldve clarified that a bit better, the miner that i meant was the one made by nicehash or for nicehash?

the cpuminer bin file. it should be like mining with sgminer to your wallet, but ive never been able to figure it out before

scratch that, got it now. since i grabbed a few blocks over the past few days i thought i would try by myself

It should work, but according to our tests, cpuminer isn't nicely optimized for getting work from wallet. The mining load on CPUs was not 100% any more, but fluctuated which reduced mining speed. I guess you would get more in pooled mining.
legendary
Activity: 964
Merit: 1000
does anyone know how to setup the QT for solo mining? i have tried adding a .conf file with a user and password to connect with, and -server=1 is there. but still no luck connecting the nicehash miner to my wallet

Won't work.. Nicehash requires stratum, the wallet is getwork.

sorry shouldve clarified that a bit better, the miner that i meant was the one made by nicehash or for nicehash?

the cpuminer bin file. it should be like mining with sgminer to your wallet, but ive never been able to figure it out before

scratch that, got it now. since i grabbed a few blocks over the past few days i thought i would try by myself
legendary
Activity: 2688
Merit: 1240
does anyone know how to setup the QT for solo mining? i have tried adding a .conf file with a user and password to connect with, and -server=1 is there. but still no luck connecting the nicehash miner to my wallet

Won't work.. Nicehash requires stratum, the wallet is getwork.
hero member
Activity: 658
Merit: 500
a fair bit of orphan blocks...
legendary
Activity: 964
Merit: 1000
does anyone know how to setup the QT for solo mining? i have tried adding a .conf file with a user and password to connect with, and -server=1 is there. but still no luck connecting the nicehash miner to my wallet
legendary
Activity: 1162
Merit: 1000
Not a single orphan all day, for over 20 hours and now 4 practically one after another. Rats!

Manually resync your PCs clock.  Tight timedrift like all POS 2.0, just trust me.


Blocks 1758961 - Forever = 1 AXIOM per block

by your logic the value of this project should be infinity.  Makes 0 sense. I do not care really if blockchain is moving faster then it was intended to. All that matters is the current number of coins the and the current price.  Thats how you value it.  You can value it however you like but I think this is the standard way and how most people do.

Yes, this is correct.  All the online marketcap indexes calculate it as current coins x current price.  Final marketcap is really useless for guiding your trading decisions in the short to medium term and 99% of your trading decisions should be short to medium term in crypto, seeing as the vast majority of coins are dead within the month.  Current market cap, emission rate, inflation, and volume are what is important.

Thank you for the tip.

I know how valuations are calculated in most cases, I just disagree with that fake "valuation". And so do markets and everyone else, naturally.

I also disagree regarding the "vast majority" being dead within a month. It may sound like a nice sound byte but, in actuality, it's meaningless and untrue. Most coin projects survive months, even years (plural), so much more than a month.

In this particular case, not taking into consideration the relatively short term by which it will be fully distributed -with the 1 coin per block forever" being only a small interest to keep the network going-, would be completely absurd EVEN if considering that the project won't survive longer than a few months. Calculating a price that, everything remaining the same, will be double simply by the amount of coins in circulation, in a month or so, is choosing to carry blinders to reality.

But hey, to each his own.
hero member
Activity: 882
Merit: 500
MiG Messenger - earn while chatting
Not a single orphan all day, for over 20 hours and now 4 practically one after another. Rats!

Manually resync your PCs clock.  Tight timedrift like all POS 2.0, just trust me.


Blocks 1758961 - Forever = 1 AXIOM per block

by your logic the value of this project should be infinity.  Makes 0 sense. I do not care really if blockchain is moving faster then it was intended to. All that matters is the current number of coins the and the current price.  Thats how you value it.  You can value it however you like but I think this is the standard way and how most people do.

Yes, this is correct.  All the online marketcap indexes calculate it as current coins x current price.  Final marketcap is really useless for guiding your trading decisions in the short to medium term and 99% of your trading decisions should be short to medium term in crypto, seeing as the vast majority of coins are dead within the month.  Current market cap, emission rate, inflation, and volume are what is important.
sr. member
Activity: 334
Merit: 250
Wow just looking around on coinmarketcap.com and this coin currenlty has a market cap of $ 44,558 at current rank of 182.

This coin is seriously undervalued right now IMO.  Give the dev some time, I for one think this coin could easily obtain 10X the market cap it has today in the near future.

That's just the way Coinmarketcap values these projects. The real valuation of this one though, at this moment, is $308,000 (10 million coins*11,000 sat*280). It is low but, everything considered, it is just conservatively low. Many, many, many people would invest heavily in this, and at much higher levels, if the ever present red flags were to be reduced or eliminated. Time is quickly running out on a few of them and for those Sunday night will just be too late.

You can say that but the current market cap is not 308,000 it is ~44,000.  The 10 million mark won't be reached for FOUR years and one month is forever in crypto so to me it make 0 sense to value a project based on its final amount of coins instead of its current.  It would seem most people agree with me since that is how coinmarketcap is setup and when you hear people talk about Bitcoins market cap they don't use 21 million mark because it won't be reached until 2140 or something.  


Oh you are VERY wrong there. The distribution is being highly accelerated and the 10 million mark will be reached -if the project survives- much, much, much earlier. Just take a look at the OP's distribution timeline and you'll see we will be there, like I said, much sooner that 4 years.

Otherwise, you can choose to value it in whichever way you want. Everyone does anyway, so why not?


Blocks 1758961 - Forever = 1 AXIOM per block

by your logic the value of this project should be infinity.  Makes 0 sense. I do not care really if blockchain is moving faster then it was intended to. All that matters is the current number of coins and the current price.  Thats how you value it.  You can value it however you like but I think this is the standard way and how most people do.
legendary
Activity: 1162
Merit: 1000
Wow just looking around on coinmarketcap.com and this coin currenlty has a market cap of $ 44,558 at current rank of 182.

This coin is seriously undervalued right now IMO.  Give the dev some time, I for one think this coin could easily obtain 10X the market cap it has today in the near future.

That's just the way Coinmarketcap values these projects. The real valuation of this one though, at this moment, is $308,000 (10 million coins*11,000 sat*280). It is low but, everything considered, it is just conservatively low. Many, many, many people would invest heavily in this, and at much higher levels, if the ever present red flags were to be reduced or eliminated. Time is quickly running out on a few of them and for those Sunday night will just be too late.

You can say that but the current market cap is not 308,000 it is ~44,000.  The 10 million mark won't be reached for FOUR years and one month is forever in crypto so to me it make 0 sense to value a project based on its final amount of coins instead of its current.  It would seem most people agree with me since that is how coinmarketcap is setup and when you hear people talk about Bitcoins market cap they don't use 21 million mark because it won't be reached until 2140 or something. 


Oh you are VERY wrong there. The distribution is being highly accelerated and the 10 million mark will be reached -if the project survives- much, much, much earlier. Just take a look at the OP's distribution timeline and you'll see we will be there, like I said, much sooner that 4 years.

Otherwise, you can choose to value it in whichever way you want. Everyone does anyway, so why not?
hero member
Activity: 602
Merit: 500
this coin so good for P&D strategy...

now i will wait my order to be executed below 8k...hope it will hit..but to be honest i love this coin..and hope dev still active on development
sr. member
Activity: 334
Merit: 250
Wow just looking around on coinmarketcap.com and this coin currenlty has a market cap of $ 44,558 at current rank of 182.

This coin is seriously undervalued right now IMO.  Give the dev some time, I for one think this coin could easily obtain 10X the market cap it has today in the near future.

That's just the way Coinmarketcap values these projects. The real valuation of this one though, at this moment, is $308,000 (10 million coins*11,000 sat*280). It is low but, everything considered, it is just conservatively low. Many, many, many people would invest heavily in this, and at much higher levels, if the ever present red flags were to be reduced or eliminated. Time is quickly running out on a few of them and for those Sunday night will just be too late.

You can say that but the current market cap is not 308,000 it is ~44,000.  The 10 million mark won't be reached for FOUR years and one month is forever in crypto so to me it make 0 sense to value a project based on its final amount of coins instead of its current.  It would seem most people agree with me since that is how coinmarketcap is setup and when you hear people talk about Bitcoins market cap they don't use 21 million mark because it won't be reached until 2140 or something.  

How do you even come up with 10 million as the number of coins? 

Blocks 1758961 - Forever = 1 AXIOM per block

It would seem to me if you want to do the math by your logic the value of this project should be infinity as coins will keep being produced as long as time goes on and the chain keeps moving.

As for me and I imagine most people I will value this project based on the current number of coins, the rate they are being produced and its current price because in crypto time moves to fast to worry about years from now.
legendary
Activity: 1162
Merit: 1000
Not a single orphan all day, for over 20 hours and now 4 practically one after another. Rats!
legendary
Activity: 1162
Merit: 1000
Wow just looking around on coinmarketcap.com and this coin currenlty has a market cap of $ 44,558 at current rank of 182.

This coin is seriously undervalued right now IMO.  Give the dev some time, I for one think this coin could easily obtain 10X the market cap it has today in the near future.

That's just the way Coinmarketcap values these projects. The real valuation of this one though, at this moment, is $308,000 (10 million coins*11,000 sat*280). It is low but, everything considered, it is just conservatively low. Many, many, many people would invest heavily in this, and at much higher levels, if the ever present red flags were to be reduced or eliminated. Time is quickly running out on a few of them and for those Sunday night will just be too late.
legendary
Activity: 2870
Merit: 1091
--- ChainWorks Industries ---
I'm trying to build the wallet from source, but getting this error:


secp256k1/src/ecmult_impl.h: In function âvoid secp256k1_ecmult_odd_multiples_table_storage_var(int, secp256k1_ge_storage_t*, const secp256k1_gej_t*)â:
secp256k1/src/ecmult_impl.h:96:71: warning: invalid conversion from âvoid*â to âsecp256k1_gej_t*â [-fpermissive]
secp256k1/src/ecmult_impl.h:97:69: warning: invalid conversion from âvoid*â to âsecp256k1_ge_t*â [-fpermissive]
secp256k1/src/ecmult_impl.h:98:67: warning: invalid conversion from âvoid*â to âsecp256k1_fe_t*â [-fpermissive]
secp256k1/src/secp256k1.c: At global scope:
secp256k1/src/secp256k1.c:460:48: warning: deprecated conversion from string constant to âchar*â [-Wwrite-strings]
secp256k1/src/field_10x26_impl.h:44:13: warning: âvoid secp256k1_fe_verify(const secp256k1_fe_t*)â defined but not used [-Wunused-function]
secp256k1/src/group_impl.h:36:13: warning: âvoid secp256k1_ge_set_infinity(secp256k1_ge_t*)â defined but not used [-Wunused-function]
secp256k1/src/group_impl.h:161:13: warning: âvoid secp256k1_gej_set_xy(secp256k1_gej_t*, const secp256k1_fe_t*, const secp256k1_fe_t*)â defined but not used [-Wunused-function]
secp256k1/src/group_impl.h:227:12: warning: âint secp256k1_gej_is_valid_var(const secp256k1_gej_t*)â defined but not used [-Wunused-function]
secp256k1/src/secp256k1.c:637:1: fatal error: opening dependency file obj/secp256k1/src/secp256k1.d: No such file or directory
compilation terminated.
make: *** [obj/secp256k1/src/secp256k1.o] Error 1


Nevermind, found part of the fix on page 4, however now I get this:



/usr/local/include/boost/filesystem/operations.hpp:508: undefined reference to `boost::filesystem::detail::rename(boost::filesystem::path const&, boost::filesystem::path const&, boost::system::error_code*)'
collect2: ld returned 1 exit status
make: *** [axiomd] Error 1


I'm using boost 1.55

do you have the all the boost dev packages installed also? ...

just a shot in the dark with that question Wink ...

#crysx
legendary
Activity: 964
Merit: 1000
Up to 300 Axiom now, lets see if i can get lucky with any stakes, Spent a bit of money on it.
sr. member
Activity: 334
Merit: 250
Wow just looking around on coinmarketcap.com and this coin currenlty has a market cap of $ 44,558 at current rank of 182.

This coin is seriously undervalued right now IMO.  Give the dev some time, I for one think this coin could easily obtain 10X the market cap it has today in the near future.
newbie
Activity: 18
Merit: 0
I'm trying to build the wallet from source, but getting this error:


secp256k1/src/ecmult_impl.h: In function âvoid secp256k1_ecmult_odd_multiples_table_storage_var(int, secp256k1_ge_storage_t*, const secp256k1_gej_t*)â:
secp256k1/src/ecmult_impl.h:96:71: warning: invalid conversion from âvoid*â to âsecp256k1_gej_t*â [-fpermissive]
secp256k1/src/ecmult_impl.h:97:69: warning: invalid conversion from âvoid*â to âsecp256k1_ge_t*â [-fpermissive]
secp256k1/src/ecmult_impl.h:98:67: warning: invalid conversion from âvoid*â to âsecp256k1_fe_t*â [-fpermissive]
secp256k1/src/secp256k1.c: At global scope:
secp256k1/src/secp256k1.c:460:48: warning: deprecated conversion from string constant to âchar*â [-Wwrite-strings]
secp256k1/src/field_10x26_impl.h:44:13: warning: âvoid secp256k1_fe_verify(const secp256k1_fe_t*)â defined but not used [-Wunused-function]
secp256k1/src/group_impl.h:36:13: warning: âvoid secp256k1_ge_set_infinity(secp256k1_ge_t*)â defined but not used [-Wunused-function]
secp256k1/src/group_impl.h:161:13: warning: âvoid secp256k1_gej_set_xy(secp256k1_gej_t*, const secp256k1_fe_t*, const secp256k1_fe_t*)â defined but not used [-Wunused-function]
secp256k1/src/group_impl.h:227:12: warning: âint secp256k1_gej_is_valid_var(const secp256k1_gej_t*)â defined but not used [-Wunused-function]
secp256k1/src/secp256k1.c:637:1: fatal error: opening dependency file obj/secp256k1/src/secp256k1.d: No such file or directory
compilation terminated.
make: *** [obj/secp256k1/src/secp256k1.o] Error 1


Nevermind, found part of the fix on page 4, however now I get this:



/usr/local/include/boost/filesystem/operations.hpp:508: undefined reference to `boost::filesystem::detail::rename(boost::filesystem::path const&, boost::filesystem::path const&, boost::system::error_code*)'
collect2: ld returned 1 exit status
make: *** [axiomd] Error 1


I'm using boost 1.55

You'll have to check some earlier posts; you must mkdir 2 directories manually to compile without error

edit: oh your problem is boost, please disregard
hero member
Activity: 979
Merit: 510
I'm trying to build the wallet from source, but getting this error:


secp256k1/src/ecmult_impl.h: In function âvoid secp256k1_ecmult_odd_multiples_table_storage_var(int, secp256k1_ge_storage_t*, const secp256k1_gej_t*)â:
secp256k1/src/ecmult_impl.h:96:71: warning: invalid conversion from âvoid*â to âsecp256k1_gej_t*â [-fpermissive]
secp256k1/src/ecmult_impl.h:97:69: warning: invalid conversion from âvoid*â to âsecp256k1_ge_t*â [-fpermissive]
secp256k1/src/ecmult_impl.h:98:67: warning: invalid conversion from âvoid*â to âsecp256k1_fe_t*â [-fpermissive]
secp256k1/src/secp256k1.c: At global scope:
secp256k1/src/secp256k1.c:460:48: warning: deprecated conversion from string constant to âchar*â [-Wwrite-strings]
secp256k1/src/field_10x26_impl.h:44:13: warning: âvoid secp256k1_fe_verify(const secp256k1_fe_t*)â defined but not used [-Wunused-function]
secp256k1/src/group_impl.h:36:13: warning: âvoid secp256k1_ge_set_infinity(secp256k1_ge_t*)â defined but not used [-Wunused-function]
secp256k1/src/group_impl.h:161:13: warning: âvoid secp256k1_gej_set_xy(secp256k1_gej_t*, const secp256k1_fe_t*, const secp256k1_fe_t*)â defined but not used [-Wunused-function]
secp256k1/src/group_impl.h:227:12: warning: âint secp256k1_gej_is_valid_var(const secp256k1_gej_t*)â defined but not used [-Wunused-function]
secp256k1/src/secp256k1.c:637:1: fatal error: opening dependency file obj/secp256k1/src/secp256k1.d: No such file or directory
compilation terminated.
make: *** [obj/secp256k1/src/secp256k1.o] Error 1


Nevermind, found part of the fix on page 4, however now I get this:



/usr/local/include/boost/filesystem/operations.hpp:508: undefined reference to `boost::filesystem::detail::rename(boost::filesystem::path const&, boost::filesystem::path const&, boost::system::error_code*)'
collect2: ld returned 1 exit status
make: *** [axiomd] Error 1


I'm using boost 1.55
Pages:
Jump to: