Please try this version, built with -DSTATIC=1 -DPORTABLE=1 in cmake, and also modified CXX_FLAGS in CMakeLists.txt to have -mno-sse4.1 and -mno-sse4.2: in more detail, in which place to insert? If that doesn't work for you, please provide the output of this command: cat /proc/cpuinfo | grep -m1 'flags' Did, I do not help all the same mistake. I'm sorry but I need to see the output of the cat command.. please provide it so I can give you a proper binary or give you instructions on what type of binary to generate. Without that information we're just guessing as to what features your processor has. Instructions with more detail --- Edit the file CMakeLists.txt, in the top-level directory. On line 80, change set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -std=c++11 ${MINGW_FLAG} ${WARNINGS} ${CXX_WARNINGS} ${ARCH_FLAG} -maes")
to set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -mno-sse4.2 -mno-sse4.1 -mno-sse4 -std=c++11 ${MINGW_FLAG} ${WARNINGS} ${CXX_WARNINGS} ${ARCH_FLAG} -maes")
If your processor also lacks sse3 (and/or ssse3), you need to also include `-mno-sse3` and `-mno-ssse3`. instead of running `cmake ..` in the build directory, instead, run `cmake -DSTATIC=1 -DPORTABLE=1 ..` |
|
|
|
Need to cmake .. from build dir, not cmake in the main src dir. Also please try only cmake with the new options first, before you modify the makefile. Tried it. Did not help. The binary daemon itself does not start. ./intensecoind: error while loading shared libraries: libboost_system.so.1.64.0: cannot open shared object file: No such file or directory Install http://www.boost.org/users/history/version_1_64_0.html./intensecoind
Illegal instruction Please try this version, built with -DSTATIC=1 -DPORTABLE=1 in cmake, and also modified CXX_FLAGS in CMakeLists.txt to have -mno-sse4.1 and -mno-sse4.2: https://github.com/valiant1x/intensecoin/releases/download/v1.0/intensecoin-miner-linux64.tar.gzIf that doesn't work for you, please provide the output of this command: cat /proc/cpuinfo | grep -m1 'flags'
|
|
|
|
Need to cmake .. from build dir, not cmake in the main src dir. Also please try only cmake with the new options first, before you modify the makefile. Tried it. Did not help. The binary daemon itself does not start. ./intensecoind: error while loading shared libraries: libboost_system.so.1.64.0: cannot open shared object file: No such file or directory Install http://www.boost.org/users/history/version_1_64_0.html./intensecoind
Illegal instruction I'm sorry the instructions didn't work as intended. The illegal instruction error is because the software was compiled with instructions your processor doesn't support. I'll try to compile the public binary without sse4.2 support for you. Firing up the VM now The VPNs most people use are purchased through centralized VPN companies.
... Could you answer my question above: what's the difference between this project and Tor except that Tor nodes are free for everyone and still are decentralised? Tor is dreadfully slow, and Tor is linked to an entire different network (onion/deepweb). It's also much more common to use Tor solely for browser proxifying rather than as a VPN, in which every connection on your computer proceeds through the network. Again, Tor might have the capability to handle non-HTTP/HTTPS apps if they are designed correctly, but they will suffer significant speed penalties. Conversely, ITNS has no initial plans to network via deep web. As I told someone on Slack, the dark/deep web has very negative connotations. People hear deep web and think of hitmen, while people hear VPNs and think of the matrix. Think of your average PC user, not highly technical and well-educated technophiles like most people on BCT. Furthermore, part of the reason Tor is slow is because it's free. There's no incentive for people to host exit nodes, other than some interest in perpetuating a free internet (not many altruistic people are out there that do this). ITNS proposes to incentivize sharing your internet connection rather than doing it "for the good" of internet anonymity and security. If the VPN can work and without major latency, slowing down the browser experience, then this project could defintiely have potential
The value of VPN is questionable when there is a corporate company you need to trust, that the govt can call into court demanding to see IP logs and records and such
If the VPN is decentralized though, there is nobody to subpoena into court
Exactly. Decentralization is IDEAL for VPNs. It's the perfect use case. Another aspect to consider with the VPN service is bandwidth control. General surfing / browsing via a VPN running through a connection is one thing, streaming 4K UHD movies is quite another. I think there needs to be something built into the product that allows a VPN provider to cap the bandwidth usage.
Good point, our proposed billing model for the client/server relationship will be in time (pay per minute) rather than bandwidth, but an option should exist for data caps. I'm glad you brought this up. Just started mining this last night, liked what I read for the future, and hoping you guys can pull it off!  And now for my reason to post, and forgive me if already addressed previously, as I've only read the past 20 pages of posts: Curious of one thing, is the "Denomination Unit: 1.000 ITNS" always going to remain for intensecoin.com/pool? I never paid attention to that mention when I started, but now that I have half a day of payouts under my belt I now realize that means I'll only ever see whole # payouts. And therefore the day I decide to cease mining/go elsewhere I'll have leftover decimal amounts remain. Sure it's only a decimal amount, for a coin with currently no value attached to it, but it'd be nice to make clean breaks from pools. Hmm, maybe down the line. |
|
|
|
will it work , I mean we already have VPNs, we pay for it, so why we invest in this COIN? , I just want a good logical answer
The VPNs most people use are purchased through centralized VPN companies. Most people don't want their activities, information and identity known by VPN companies. After all, most people use VPNs for anonymity. ITNS will offer a solution to this, and offer VPN anonymity because the endpoint of your VPN is not some large provider forced to keep records on clients. In most cases it will be a user at their house, or someone with dedicated or VPS hosting. We cut out the middleman of requiring a VPN company and instead make the VPN a Peer-to-Peer (P2P) process. Furthermore, the P2P mechanism allows users to generate revenue (in ITNS) for allowing others to use their connection, creating a consumer-driven marketplace. Also consider that centralized VPN providers allow companies and countries to easily perform sweeping blocks toward IPs used by the VPN company. This defeats the purpose of using a VPN since the nodes are inaccessible. With a P2P decentralized VPN network, it's impossible to categorically ban IPs as being accessed for providing VPN services. Consider this in the context of China, NK and other countries banning VPN use. The potential of a distributed, decentralized, P2P VPN system is much greater in terms of broad accessibility than single centralized providers. It sounds great, and VPN's on the blockchain are only inevitable, I also love the fact this is A. on Cryptonight and B. PoW...That being said, allowing people to be peer-to-peer VPN's is great and all, but doesn't that pose a risk if someone else is doing malicious activities on their end through you? So you essentially get PoS/Stake by allowing others to utilize your server/wallet/peer network but that also assumes some risk doesn't it? Also, I'm not happy to see a standard "cryptonight whitepaper" on the site, this project should have a detailed whitepaper of their own. Operating VPNs is indeed a risk, no way around that. We have plans for a whitepaper in our roadmap (October). |
|
|
|
Add Makefile build-release: cmake-release
cd build/release && $(MAKE) -DHAVE_SSE42 -msse4.2 intensecoin-master# rm -rf build
root@xci:/home/max/intensecoin-master# cmake -DPORTABLE=1 -DWITH_AVX2=0
-- Boost version: 1.55.0
-- Found the following Boost libraries:
-- system
-- filesystem
-- thread
-- date_time
-- chrono
-- regex
-- serialization
-- program_options
CMake Error at /usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:108 (message):
Could NOT find Threads (missing: Threads_FOUND)
Call Stack (most recent call first):
/usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:315 (_FPHSA_FAILURE_MESSAGE)
/usr/share/cmake-2.8/Modules/FindThreads.cmake:166 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
external/rocksdb/CMakeLists.txt:319 (find_package)
-- Configuring incomplete, errors occurred!
See also "/home/max/intensecoin-master/CMakeFiles/CMakeOutput.log".
See also "/home/max/intensecoin-master/CMakeFiles/CMakeError.log".
Need to cmake .. from build dir, not cmake in the main src dir. Also please try only cmake with the new options first, before you modify the makefile. |
|
|
|
will it work , I mean we already have VPNs, we pay for it, so why we invest in this COIN? , I just want a good logical answer
The VPNs most people use are purchased through centralized VPN companies. Most people don't want their activities, information and identity known by VPN companies. After all, most people use VPNs for anonymity. ITNS will offer a solution to this, and offer VPN anonymity because the endpoint of your VPN is not some large provider forced to keep records on clients. In most cases it will be a user at their house, or someone with dedicated or VPS hosting. We cut out the middleman of requiring a VPN company and instead make the VPN a Peer-to-Peer (P2P) process. Furthermore, the P2P mechanism allows users to generate revenue (in ITNS) for allowing others to use their connection, creating a consumer-driven marketplace. Also consider that centralized VPN providers allow companies and countries to easily perform sweeping blocks toward IPs used by the VPN company. This defeats the purpose of using a VPN since the nodes are inaccessible. With a P2P decentralized VPN network, it's impossible to categorically ban IPs as being accessed for providing VPN services. Consider this in the context of China, NK and other countries banning VPN use. The potential of a distributed, decentralized, P2P VPN system is much greater in terms of broad accessibility than single centralized providers. |
|
|
|
Try running cmake with -DPORTABLE=1 -DWITH_AVX2=0 Did not help, the mistakes are the same. Did you `rm -rf build` first, before running `cmake -DPORTABLE=1 -DWITH_AVX2=0 ..` ? Which version of cmake are you using? Please also try running cmake with `-DHAVE_SSE42 -msse4.2 `. If that doesn't work, open the Makefile and add those arguments like so: previous: build-release: cmake-release
cd build/release && $(MAKE)
new: build-release: cmake-release
cd build/release && $(MAKE) -DHAVE_SSE42 -msse4.2
Sorry, it wasn't making new blocks for about an hour. The VPS it is hosted on seems to get cranky after 7-10 days and requires the daemon be restarted. It's running smoothly now. |
|
|
|
I do not know the password for my wallet. Talked to you on slack via DM, you should be sorted now. My apologies for the troubles. To anyone now reading this message, I have asked alex to update the original post with new wallet links -- please only use the new wallet 1.2 from https://github.com/valiant1x/intensecoinwallet/releases ! Also, as mentioned on Slack and on the pool site: Please note that in 3 days time (on 23/9/17) we will be increasing the pool fee to encourage network diversity and promote network health. |
|
|
|
Need help in run daemon.
No start , libbost 1.64, installed, no start illegal instruction.
No compilled, error.
Ubuntu 14.04 x64.
Did you manage to fix this? I can't compile it under Ubuntu 14.04 64-bit either.. Without specific compilation errors we cannot help. We need output of the errors, specific the errors and we can gladly help. Cheers -- Configuring incomplete, errors occurred!
See also "/home/max/intensecoin-master/build/release/CMakeFiles/CMakeOutput.log".
See also "/home/max/intensecoin-master/build/release/CMakeFiles/CMakeError.log".
make: *** [cmake-release] Error 1 CMakeOutput.log The system is: Linux - 3.13.0-129-generic - x86_64
Compiling the C compiler identification source file "CMakeCCompilerId.c" succeeded.
Compiler: /usr/bin/cc.
Build flags:.
Id flags:.
The output was:
0
Compilation of the C compiler identification source "CMakeCCompilerId.c" produced "a.out
The C compiler identification is GNU, found in "/home/max/intensecoin-master/build/relea
Compiling the CXX compiler identification source file "CMakeCXXCompilerId.cpp" succeeded
Compiler: /usr/bin/c++.
Build flags:.
Id flags:.
The output was:
0 CMakeError.log erforming C++ SOURCE FILE Test HAVE_SSE42 failed with the following output:
Change Dir: /home/max/intensecoin-master/build/release/CMakeFiles/CMakeTmp
Run Build Command:/usr/bin/make "cmTryCompileExec4143452986/fast"
make[1]: Entering directory `/home/max/intensecoin-master/build/release/CMakeFiles/CMake
/usr/bin/make -f CMakeFiles/cmTryCompileExec4143452986.dir/build.make CMakeFiles/cmTryCo
make[2]: Entering directory `/home/max/intensecoin-master/build/release/CMakeFiles/CMake/usr/bin/cmake -E cmake_progress_report /home/max/intensecoin-master/build/release/CMake
Building CXX object CMakeFiles/cmTryCompileExec4143452986.dir/src.cxx.o
/usr/bin/c++ -pthread -std=c++11 -Wall -Wextra -Wpointer-arith -Wundef -Wvla -Wwrite
In file included from /home/max/intensecoin-master/build/release/CMakeFiles/CMakeTmp/src/usr/lib/gcc/x86_64-linux-gnu/4.8/include/nmmintrin.h:31:3: error: #error "SSE4.2 instru
# error "SSE4.2 instruction set not enabled"
^
/home/max/intensecoin-master/build/release/CMakeFiles/CMakeTmp/src.cxx: In function ‘int
/home/max/intensecoin-master/build/release/CMakeFiles/CMakeTmp/src.cxx:5:43: error: ‘_mm
volatile uint32_t x = _mm_crc32_u32(0, 0);
^
/home/max/intensecoin-master/build/release/CMakeFiles/CMakeTmp/src.cxx:5:21: warning: un
volatile uint32_t x = _mm_crc32_u32(0, 0);
^
make[2]: Leaving directory `/home/max/intensecoin-master/build/release/CMakeFiles/CMakeT
make[2]: *** [CMakeFiles/cmTryCompileExec4143452986.dir/src.cxx.o] Error 1
make[1]: Leaving directory `/home/max/intensecoin-master/build/release/CMakeFiles/CMakeTmp'
make[1]: *** [cmTryCompileExec4143452986/fast] Error 2
Source file was:
#include <cstdint>
#include <nmmintrin.h>
int main() {
volatile uint32_t x = _mm_crc32_u32(0, 0);
}
Performing C SOURCE FILE Test HAVE_FALLOCATE failed with the following output:
Change Dir: /home/max/intensecoin-master/build/release/CMakeFiles/CMakeTmp
Run Build Command:/usr/bin/make "cmTryCompileExec3248412868/fast"
make[1]: Entering directory `/home/max/intensecoin-master/build/release/CMakeFiles/CMakeTmp'
/usr/bin/make -f CMakeFiles/cmTryCompileExec3248412868.dir/build.make CMakeFiles/cmTryCompileExec3248412868.dir/build
make[2]: Entering directory `/home/max/intensecoin-master/build/release/CMakeFiles/CMakeTmp'
/usr/bin/cmake -E cmake_progress_report /home/max/intensecoin-master/build/release/CMakeFiles/CMakeTmp/CMakeFiles 1
Building C object CMakeFiles/cmTryCompileExec3248412868.dir/src.c.o
/usr/bin/cc -std=c11 -Wall -Wextra -Wpointer-arith -Wundef -Wvla -Wwrite-strings -Werror -Wno-error=extra -Wno-error=unused-function -Wno-error=deprecated-declarations -Wno-error=sign-compare -Wno-error=strict-aliasing -Wno-error=type-limits -Wno-unused-parameter -Wn
cc1: error: command line option ‘-Wno-reorder’ is valid for C++/ObjC++ but not for C [-Werror]
cc1: error: command line option ‘-std=c++11’ is valid for C++/ObjC++ but not for C [-Werror]
cc1: all warnings being treated as errors
make[2]: Leaving directory `/home/max/intensecoin-master/build/release/CMakeFiles/CMakeTmp'
make[2]: *** [CMakeFiles/cmTryCompileExec3248412868.dir/src.c.o] Error 1
make[1]: Leaving directory `/home/max/intensecoin-master/build/release/CMakeFiles/CMakeTmp'
make[1]: *** [cmTryCompileExec3248412868/fast] Error 2
Source file was:
#include <fcntl.h>
#include <linux/falloc.h>
int main() {
int fd = open("/dev/null", 0);
fallocate(fd, FALLOC_FL_KEEP_SIZE | FALLOC_FL_PUNCH_HOLE, 0, 1024);
}
Determining if the function malloc_usable_size exists failed with the following output:
Change Dir: /home/max/intensecoin-master/build/release/CMakeFiles/CMakeTmp
Run Build Command:/usr/bin/make "cmTryCompileExec1014184147/fast"
make[1]: Entering directory `/home/max/intensecoin-master/build/release/CMakeFiles/CMakeTmp' This is due to your processor being old and not supporting new instructions found in new CPUs. Try running cmake with -DPORTABLE=1 -DWITH_AVX2=0 can we now use the wallet optimization on the new gui wallet or not?
No. Wallet will be patched soon to disallow. Is there anything I can do about an unconfirmed transaction that I sent before I updated to the new wallet? The fee was too low and it's been almost a week. Transaction: 5b6f82ca45c918c8b6b4743e765c49226af9c53a16224484f826e36813ab5ebb
It's not showing up in the transaction pool so I'm not sure it's actually still trying to make it out to the network - did you try resetting the wallet (File > Reset wallet)? VALIANT1!!! since you've been active and ignored my post and ignored me on the slack, here it is again...So after doing everything the dev suggested, upgrade wallet, turn off wallet optimization (which was never turned on), take wallet offline for a couple of days, I still have about 18000 coins locked. I need answers regarding this, you cant expect everyone to keep mining and we cant get our coins, there are guys on the slack group who have 40000 coins locked.... Do you have a fix? are you working on a fix? everytime anyone has a problem with the wallet your answer is always the same, "have you tried to reset?" we have reset many times and it does not work!! My apologies for not following up on the posts here. As was mentioned in Slack I will gladly reply to any DMs or mentions @intense-valiant. You and I are also talking via DM in Slack to resolve. At this time I am awaiting requested logs from you. |
|
|
|
Is there anything I can do about an unconfirmed transaction that I sent before I updated to the new wallet? The fee was too low and it's been almost a week. Transaction: 5b6f82ca45c918c8b6b4743e765c49226af9c53a16224484f826e36813ab5ebb
It's not showing up in the transaction pool so I'm not sure it's actually still trying to make it out to the network - did you try resetting the wallet (File > Reset wallet)? |
|
|
|
Selected highlights:- the pool mining server and daemon have been running for weeks without complaint
- At this time, we are still waiting for response from NovaExchange regarding listing, as their 1 BTC listing fee is something the core team is able to budget out of personal coffers
- development has not been tremendously fruitful as of late
- active on Twitter and Bitcointalk
- Going forward, we plan to publish a monthly summary of the happenings of Intense Coin, on or about the 15th of the month (the launch anniversary of Intense).
- Following our roadmap, the items on our immediate agenda are paper wallet generation (a la BIP39), ITNS listing on an exchange, a Slack tipbot, and a Twitter awareness ad campaign
AnalysisFirst the bad stuff: development of the VPN solution not being fruitful is a little concerning. This project has a lot of potential but it'll require a credible path to actually building the VPN solution. That said it's only been a month and we should see how things stand over the next few ones. The good stuff: The developers are willing to pay 1 BTC out of their person pockets to get it listed. That shows a serious commitment by the developer, and so, per my previous point, even if they didn't have a great first month, it shows that they intend to make some true progress. Moreover the promise to provide monthly updates is also a really positive move. Open and clear communication will build a lot of trust and interest in the project. It's like a company publishing quarterly reports. All in all in my mind this update substantially boosted the value of this coin. Before we kind of just had to take it on face value that a VPN solution would be built. Now we have some evidence that developers are both serious about it and will give us honest updates about its development. SyrioForElle, thanks very much for your comprehensive summary and analysis. I would ask for your reconsideration of labeling the lack of VPN progress as concerning. Unanticipated and exorbitant amounts of time and resources were dedicated to resolving and maintaining issues with the core branch after launch. We used the CryptoNote reference implementation, thinking that was the best as it's right from the CN foundation and developers, but in fact it turned out to be neglected and rife with issues. Upgrading the core code, the pool software, and triaging all of the snags that came about as a result of those actions tied us up from time that should have been spent on VPN-related activities. I am not stating these facts to be defensive, but to hopefully share insight for the uninitiated on the reasons behind our current delayed status. We have now patched up these issues and feel, at last, pleased with the coin itself, leaving us to focus on more important matters (the actual development of the VPN service)! Also note that there have been efforts mentioned to discuss the work with private contacts and some VPN companies, so it wasn't a complete wash.  R&D continues. At this very moment I am consulting with a firm that has worked on a similar project. While it took longer than we would like to get to this point, as you said it has only been a month, and we are working diligently to have significant progress in the VPN arena by the next monthly report. We appreciate your positivity and support. |
|
|
|
Very well developed Roadmap. Many miners at the pool http://intensecoin.com/pool/#. I also used this pool and I have something over 30k intensecoins. I look forward to coinexchange now in September and to cryptopia or livecoin in October. Many times I've been selling before the official exchange and then I regret. For now, I have left coins and I do not sell. But it's up to each miner what will to do with coins. I wish many achievements for dev team. But also for us miners. Made for the community:  Very cool!!! Thanks, oli123! I hope you continue to HODL, and I hope it's rewarding for you. If we continue to execute our plans as proposed, I am sure you will be pleased with your decision. Hey, this means you are using the wrong binary version for your platform. At the time you posted, only x86_64 binaries were available, which is for 64-bit linux. I have now uploaded the 32-bit daemon binaries here which should solve your problem. I have Ubuntu 14.04. x64 You're definitely best off compiling from source as mentioned above ,but just out of curiosity, what's the output of uname -a? |
|
|
|
./intensecoind
Illegal instruction
Dev need help, please. Hey, this means you are using the wrong binary version for your platform. At the time you posted, only x86_64 binaries were available, which is for 64-bit linux. I have now uploaded the 32-bit daemon binaries here which should solve your problem. OK first I apologise. 1. It seems that Im using tha 1.0 wallet it was on the main website of Intensecoin, (although Ive read the mandatory wallet update) an downloaded the wallet that was in the link of the main website (But the devs did not updated the link rigt away I guess, thanks guys) 2. I have about 79k Coins (10k is in Unconfirmed status) What I have to do now? should copy my .wallet paste it in the directory of another laptop In wich i have installed the "fancy" new wallet 1.2.0? and press Open wallet? Or should I try to send them to the new adress of the new wallet *1.2.0 3. The old wallet works perfectly with pool synch why the update? Ive send from Rig one that used the wallet 1.0 to main Wallet also 1.0 1000 coins they went fine as usually, 10k got stuck, On which end is the problem of the wallet that had send the coins or the Wallet that received the 10k coins? 4. Sorry for the question for the 3rd time, What Should I do about the 10k uncofirmed coins that are in the Wallet 1.0? where do I find the .wallet? this is the https://github.com/valiant1x/intensecoinwallet/releases/download/v1.2/Intensecoin-win64.zip wallet that i need to Update to right? im also having endless problems with the wallet and coins getting stuck. dev just says the same thing, turn of optimization, did that, no difference, not really helpful at all... Hi, as mentioned above there is definitely a need for a command to zap TX's - in the interim, if you really want those gone, take your wallet offline. I suspect the only reason they keep coming back is that your wallet keeps sending the TXs to the network, from BEFORE you disabled optimization, and then network is rejecting them. So either load a different wallet file or close your wallet entirely, for at least a full 24 hours. Transactions live in the pool for 24 hours. Also, there is some confusion about unconfirmed vs locked txns. The instructions I just mentioned above only apply to locked coins. The only reason you will have locked coins is from optimization transactions. Unconfirmed txns, on the other hand, are due to other people sending you txns with bad information - either not enough fee, or from an outdated version of the wallet. This can also occur if you received a payment from other peoples' pools before they were using the correct code. I know kiramine has some bad payments out there. I think that pool site fixed their issue, but the unconfirmed txns will linger in your wallet until you open the wallet file in the newest GUI wallet, and select "File -> Reset wallet". @candyiman - that's the correct download link. File -> Reset wallet. The .wallet file by default is stored in ~/.intensecoin on linux/mac or %userprofile%\appdata\roaming\intensecoin on windows. |
|
|
|
sudo apt-get install libboost-system-dev package buddy
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package package
E: Unable to locate package buddy ? remove "package buddy" sudo apt-get install libboost-system-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
libboost-system-dev is already the newest version.
The following packages were automatically installed and are no longer required:
apt-xapian-index aptitude-common gccxml laptop-detect libclass-accessor-perl
libcwidget3 libept1.4.12 libio-string-perl libparse-debianchangelog-perl
libsigc++-2.0-0c2a libsub-name-perl libxapian22 python-debian python-dev
python-xapian python2.7-dev
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. My apologies, looks like the boost lib was not properly statically linked to the binaries. I'll resolve that soon. In the interim, if you want to use precompiled binaries on unix, sorry but the apt version of libboost-system-dev is out of date with what the project was compiled with. You will need to download/install boost 1.64 from www.boost.org. RE wallet issues --- transactions from 1.0 wallet will not send, sorry. https://intensecoin.com/2017/08/31/mandatory-wallet-update-ticker-change/If you want to eliminate those old broken transactions, open your .wallet file in the new 1.2 wallet, and then File->Reset wallet. Whomever mentioned using zapwallettxes command, we do not have that in our software, perhaps you're thinking of a different coin. Running `reset` in simplewallet or file->Reset in the GUI wallet should accomplish the same thing. However, it seems this is still allowing some transactions to linger - I will add a command or option to zap all pending TXs. |
|
|
|
can we use the alpha wallet to send out coins? if not what wallet do we need to send coin? because you said dev that the current wallet can not send out coin
YES The only software that will NOT properly send coins is the old Qt wallet (v1.0), or the old daemon software if you still have that downloaded (although we have taken down those download links so nobody should have the old daemon). RE DNS issues last night - the data center had a UPS-A failure. Downtime was ~10 minutes. Only the pool website/front-end was down. Pool shares continued to be recorded as those are on another server. Sorry! i still have unconfirmed coins, about 1600 thats stuck...
iz57mBcwEGdgs9epj2eTMSJ7tVL85h7bqQnBXAQuwgEZeHJFcQxYXWyTe2XLpxc3abKZ44jKMLMPTAx GeNoNEdhn28wycdUBC
thats the wallet address, could someone check please
If these are LOCKED coins that you previously owned, it's due to 'wallet optimization' transactions - you need to disable in preferences, and probably take your wallet offline for a full day before the transaction will disappear. Mind that this option is disabled by default. If this is an incoming payment that is unconfirmed, it's because the sender did not update to the latest wallet before trying to send your payment, and the TX will never confirm. Again File > Reset wallet to eliminate it from your list. mmh i don't know if i have that old qt wallet, it tell me version 1460368, what version is this? this is the version from your front first post Yep as someone else said above, just upgrade to the alpha (1.2.0) and you will be good When can the new wallet be available?Looks nice!
Available now! https://github.com/valiant1x/intensecoinwallet/releases/download/v1.2-alpha/Intensecoin-win64-12alpha-RC2.zip |
|
|
|
can we use the alpha wallet to send out coins? if not what wallet do we need to send coin? because you said dev that the current wallet can not send out coin
YES The only software that will NOT properly send coins is the old Qt wallet (v1.0), or the old daemon software if you still have that downloaded (although we have taken down those download links so nobody should have the old daemon). RE DNS issues last night - the data center had a UPS-A failure. Downtime was ~10 minutes. Only the pool website/front-end was down. Pool shares continued to be recorded as those are on another server. Sorry! i still have unconfirmed coins, about 1600 thats stuck...
iz57mBcwEGdgs9epj2eTMSJ7tVL85h7bqQnBXAQuwgEZeHJFcQxYXWyTe2XLpxc3abKZ44jKMLMPTAx GeNoNEdhn28wycdUBC
thats the wallet address, could someone check please
If these are LOCKED coins that you previously owned, it's due to 'wallet optimization' transactions - you need to disable in preferences, and probably take your wallet offline for a full day before the transaction will disappear. Mind that this option is disabled by default. If this is an incoming payment that is unconfirmed, it's because the sender did not update to the latest wallet before trying to send your payment, and the TX will never confirm. Again File > Reset wallet to eliminate it from your list. |
|
|
|
I guess there is something wrong.
Blocktime is arround 15 minutes but the difficulty is still growing.That's probably due to the today's hashrate peak between 02 and 03 GMT (over 5Mh/s), but the algo should adapt and adjust the diff faster.
I am hearing a lot of questions about block difficulty mentioned here and in Slack. I'll try to clarify.
CryptoNote derived coins adjust difficulty based on the time it took to hash the last day's worth of blocks (720 blocks in our case), minus 8.3% of outliers on each end (~17% total). It will take time for the network to re-adjust after someone pointed a lot of hashing power at the pool. The coin is always attempting to target a block time of 120 seconds based upon those last 720 blocks.
This scenario will become increasingly less common and probable as the network grows. It is vulnerable to an influence like this due to the immaturity of the blockchain and the lack of hashing power, especially as most hashing power is concentrated in a single pool. For now, this is our reality.
The difficulty adjustment algorithm works quite well. It will work better once the coin is more established. For now, we will have periods of fluctuation due to the factors described above. Network hash rate as displayed on the pool is calculated as a function of the last X blocks, just like difficulty. It's not necessarily representative of the true hash rate if people only momentarily direct TONS of hashing power at the network for a short period of time (which is what happened yesterday).
To address the questions about 'why no block explorer at launch' - I'm not sure it's really necessary with a young network. The vast majority of transactions are just mined coins, especially before the coin is on an exchange and has more value associated with it. We had our hands full with other matters and wanted to offer the community an opportunity to engage and receive a handsome bounty. Nobody was able to fulfill the bounty so we took care of the task. Regardless, it's done now |
|
|
|
In my wallet, it shows that
Available 1,322.00
Locked 5,858.00
Total 7180.30
Tried reset, blockchain is loaded normally, but then again Locked.
How do I fix the situation?
Mine started on Aug. 17, so this is not a fork.
My wallet version 1.2.0 alpha
in old version, is OK
Please disable wallet optimization in the Preferences window. I am assuming this is the cause of your problems. If that's the case, reset your wallet (File -> Reset wallet) once more after disabling that. Hi, I somewhere read that the dev was gone for some time. Is that true or has the situation been resolved by now?
Has far has i know the dev has never been gone for any period of time since the coin launch. They have been very active in the slack channel, help anyone that have any kind of problems or questions, so feel free to join and ask them anything directly... 
I think we are ready to bump the current alpha 1.2 wallet to a regular release. I have not received many reports of issues with usage or stability of the wallet. Initially we were informed of some crashes so code was put out to address that. Otherwise, things seem to work well. Another few days and we will update download links etc.
If you have not already, please consider testing our 1.2 alpha wallet; all download links are here: https://github.com/valiant1x/intensecoinwallet/releases
I also have made some progress on a block explorer (thanks Forknote!). The block explorer was a big hurdle in getting listed on an exchange. So to everyone inquiring 'when exchange???', the answer is still 'soon,' but now it is sooner! |
|
|
|
Guys, you arguing with valiant is wrong on so many levels. As some of you mentioned a good dev spends most of the time on tech development and has little interaction with the community besides solving urgent and critical technical issues. In fact, I would much prefer valiant to work on the coin and alex handle the PR. It is impossible to develop anything if you are trying to sit on more than one chair and are constantly distracted. In the end you are the ones benefiting from the potential success of the project so stop bugging valiant.
It would be helpful to create a bug tracking system for submission and progress tracking, which community members will check first before messaging the team members.
Thanks very much for your thoughts and support, Azzi. RE bug tracking - Yes, outstanding idea!! I have enabled the 'Issues' tab on the Git projects (oops, this should have been done already!).
Please report all issues with the command-line interface (intensecoind, simplewallet, walletd, etc.) to the intensecoin github and issues with the graphical wallet to the intensecoinwallet github. |
|
|
|
02-09-17 1300 UTC: The pool is running again following some daemon code adjustments for block sizes. Thanks for your patience. http://intensecoin.com/pool/
DigDeepMining, I apologize but I don't have time or patience to keep reiterating what was previously stated in the thread. Not to mention in the roadmap there is an image depicting a very specific exchange (coinexchange).
NO NEED TO SHOUT AND BE A IDIOT ABOUT IT BECAUSE PEOPLE ARE ASKING QUESTIONS!!!I defended this coin when people kept calling it shit coin telling them give it time, but then I keep seeing people asking a different questions, most if not all of which never get a reply. Yeah we all seen the road map but it doesn't really tell us anything about exchanges no ETA no nothing, yeah I could make a coin and say its gonna be on x, y and z exchanges doesn't mean it going to be and doesn't give anyone any real info. I appreciate you might be busy developing the coin etc but if you can't be bothered or have the time to answer the public's questions maybe you should look to bring in more help before everyone losses interest/hope in your coin
Please understand that we want to be on an exchange, just like you want us to be on an exchange. These things take time. Especially with how many issues we have encountered with pool and transaction stability. No sense in putting the cart before the horse. We need to make sure our code, coin and pools are STABLE before we create further chaos by introducing exchanges into the mix. It's part of our roadmap and plans, but it takes time. The exchange was slated for September, and it's only been September for a couple days. Do not worry, it's still on our agenda.
Just a few days ago, we announced a ticker change from INT to ITNS because a few people shared some old news posts about 'INTCoin' being an ICO scam from some time ago. If we had already been listed on exchanges when we tried to make this change, it would have been much more complicated and confusing. We are taking things in stride at a pace that is reasonable. We don't want to repeat mistakes from our first launch day (hard fork) and rush things. Hastiness yields no reward in this arena.
You're right, you deserve answers and information. I was under the impression it was already established (in previous posts and the main post) that we would be using coinexchange.io initially. I will update you on this and say we are also considering HitBTC for the initial listing. We will then be expanding to Cryptopia and/or Livecoin in the following month.
Another reason for the delays and somewhat silence on the matter is we are still yet to find anyone interested in hosting a block explorer for the coin. CryptoNote uses different methods than BCT-based coins and requires a bit more work to host a BE, as the code is not just plug-and-play. We would prefer that a third party host the BE for obvious reasons (conflict of interest). At this point it looks like I may need to code one since we have failed to receive a response from any of the normal CryptoNote BE hosts - ChainRadar, Minergate, Democats. This is another bump in the road and will introduce further delay into exchange plans.
Dev, how is Intense different from let's say Mysterium?
What are the pros, etc?
This is a great question I will respond to when I have some more time to compose a thoughtful response. Quoting you here so I do not forget!
|
|
|
|
|
Show Posts
